Best for: Analytics, business intelligence, and engineering teams · Uses: your own CSV data plus Botify's editable data catalog
Overview
Search performance on its own does not say what a traffic change is worth in revenue. Botify MCP's editable data catalog lets you upload your own business data and query it alongside Botify tables in one workspace.
Prerequisites
Botify MCP connected to your AI assistant, such as Claude or ChatGPT. See Connecting to the Botify MCP for setup steps.
Your own business data (for example, revenue or margin by URL or category) in a CSV file.
Description of the problem
Sizing total organic opportunity, or building a report that combines search and crawl data with your own business data, means joining two separate systems by hand every time the question comes up.
Application
Upload your own revenue or margin data as a CSV file into Botify MCP's editable data catalog. This is the same catalog behind Botify's custom tables — see Custom Tables Overview for what it can hold.
Ask your AI tool to join that data with Botify's tables:
Load this revenue CSV and join it against our crawl data by URL.
Why this prompt works:
Naming the join key (URL) explicitly is what lets your AI tool line up two systems that were never designed to talk to each other, without you writing the join logic by hand.
Uploading the CSV into Botify MCP's own data catalog, rather than pasting figures into the conversation, is what makes the data queryable alongside Botify's tables instead of a one-time reference.
Build a report that sizes your organic opportunity or shows revenue impact by category.
Follow-up prompts
"Break the revenue impact down by category instead of by URL." — rolls the same join up to a level a stakeholder report can use.
"Show me the URLs with the highest crawl activity but the lowest revenue." — turns the join into a prioritization question rather than just a report.
Make it repeatable
Keep your revenue CSV's column structure (URL, revenue or margin) consistent every time you upload it, so the join and the report built on it don't need to be rebuilt from scratch each cycle.
Result
Because the URL is the identifier your crawl data, your revenue system, and your content stack all share, it serves as the join key between them without a separate reporting pipeline.