Find every town page a competitor has and you don't, with Claude

Start here: paste this into Claude Code

Install Claude Code first if you don't have it (step 1 under “Connect Context.dev to Claude Code” below), and make your free account at context.dev (no card). Then run these lines in your terminal: they make a folder, plug Context.dev in, and start Claude. Inside Claude Code, type /mcp, pick context and sign in in your browser. Then paste the prompt. It walks you through the rest and asks before anything spends a credit.

Using the Claude app instead? Do “Or: connect it to the Claude app” below, then paste the same prompt into a new chat with Context.dev switched on.

The setup prompt (copy all of it) · lines 1-1 of 36. Copy all copies the whole prompt; read it in full on the page.

About me: I run a home-service business and I'm not technical, so use plain words and short sentences.

How the pieces connect

This is the manual way: every step, every command and every price. Claude follows it too.

Words you'll see

• MCP: a connector that lets Claude use another app. Context.dev's lets Claude read websites.
• Claude Code: Anthropic's AI assistant that works in a folder on your computer. You talk to it in plain English inside a terminal (the text-only window where you type commands).
• Connector: what the Claude app calls an MCP you've added.

• Context.dev: a web-data service for AI tools. It scrapes, crawls, searches and maps websites. This guide uses one of its tools.
• web-map (a site map): Context.dev's tool that lists a website's page addresses with their titles, from its index (its stored record of what's on the web). It doesn't open the pages themselves.

• Credit: how Context.dev charges. A site map is 1. The free plan gets 1,000 a month.
• Domain: a website's address without the https://, like yoursite.com.
• Town page (or service area page): a page about your work in one town, like “Roof replacement in Davie”.

• urlRegex: a filter that keeps only the page addresses that match a pattern. Context.dev uses a pattern style called RE2.

Connect Context.dev to Claude Code

Install Claude Code (skip if you have it)

Skip this if claude --version already prints a version. You need a paid Claude plan: Pro, Max, Team or Enterprise. The free plan doesn't include Claude Code. The first time you run claude, it sends you to your browser to log in.

Make your free Context.dev account

Create a free account. The free plan is 1,000 credits a month, one request at a time, and no card.

Make a folder for this

Your rules file and your build lists land in here, not all over your computer. If the folder's already there, mkdir complains; ignore it.

cd ~
mkdir town-pages
cd town-pages

Plug Context.dev in

That's the one command from the video. --scope user adds it for every folder on your computer, which is how Context.dev's own instructions do it. Want it in this folder only? Use the second line instead (Claude Code calls that the local scope). Pick one, not both.

Sign in

Pick context in the list and sign in to Context.dev in your browser. Rather skip the menu? claude mcp login context at the plain terminal prompt runs the same sign-in.

/mcp

Check it's there

At the plain terminal prompt, claude mcp list shows context. If it says ! Needs authentication, do the sign-in step again. Or just ask Claude: “What Context.dev tools do you have?” You should see web-map, web-scrape, web-crawl, web-search and get-usage among them.

claude mcp list

Write CLAUDE.md: the rules Claude follows every time

Here's the thing: Context.dev charges the moment a tool runs. It doesn't ask first. So the asking is Claude's job, and this file is where you tell it. Claude Code reads it at the start of every session. It's an instruction, not a lock, so watch the first few calls and say no if it skips the price.

CLAUDE.md · Part 1 of 2 · Copy copies all 22 lines

# Town pages: me vs a competitor

This folder compares my website's town and service pages with one competitor's, using Context.dev's web-map (it lists a site's pages and their titles).

## My business
- Website: <yoursite.com>
- What I sell: <your services>
- The competitor I compare with: <theirsite.com>

## Every Context.dev call
1. Tell me the tool, the website and the credits first (web-map: 1, or 2 with a search phrase), and wait for my yes.
2. After it runs, tell me what it cost (credits_consumed) and what's left (credits_remaining).
3. web-map and get-usage only, unless I ask. Never create a monitor: it spends credits every time it runs.
4. If a result is cut short (truncated), stop and suggest a urlRegex filter (RE2: no lookahead or lookbehind).

CLAUDE.md · Part 2 of 2 · Copy copies all 22 lines

## Never
- Never invent a page, a town or a number. Only what the maps show.
- Never say a page ranks or gets calls. The map can't tell.
- Never put pages named after a person (customers, reviews, team) in a table or a file.
- Never copy the competitor's wording into my build list.
- Never retry a failing call over and over. Stop and tell me.
- Never ask me for, print or save a key, token or password.

Or: connect it to the Claude app (no terminal)

Works in Claude on the web and in the desktop app, including the free Claude plan, which allows one custom connector. No folder and no CLAUDE.md here, so the rules ride along in the setup prompt. (Context.dev's install page says it's also in Claude's connector directory. The custom connector way below works either way.)

Open Connectors

Go to Customize, then Connectors.

Add Context.dev as a custom connector

Click + Add, then Add custom connector. Name it Context, paste the address below and click Continue. Claude shows the sign-in settings it found; click Continue again.

https://mcp.context.dev/mcp

Sign in and finish

Under Authentication, pick Sign in now. Keep the sign-in settings Claude found, and leave Request headers empty: that box is for API keys, and you're signing in through the browser instead. Click Add, then sign in to Context.dev in the window that opens. If no window opens, find Context in your connectors and click Connect. (Context.dev's own page shortens all this to: +, Add custom connector, the address, Connect.)

Switch it on in a chat

Start a new chat, click the + button at the lower left, then Connectors, and make sure Context is on. Then paste the setup prompt from “Start here”. Claude's help center says to pick Allow always only for tools you trust to run unsupervised. At 1 credit a map it's not about the money; I'd still say yes one call at a time, so you know exactly what ran.

On a Team or Enterprise plan

An Owner adds it once for everyone: Organization settings, Connectors, Add, hover over Custom, pick Web, then the same name and address. Everyone else goes to Customize, Connectors, finds Context and clicks Connect.

First test: your balance (free), then your own site (1 credit)

Checking your balance costs nothing, and mapping your own site costs 1 credit. Start there: it's your site, so you'll know right away if the list looks wrong. Paste this into Claude Code (or your Claude chat with Context on).

Prompt: the first test

Use Context.dev. Run get-usage (it's free) and tell me my credit balance and when it refills.

Then ask me before you spend anything. After my yes, run web-map on <yoursite.com>. Tell me what it cost (credits_consumed) and what's left, how many pages it found, and sort them into kinds: town pages, service pages, blog posts, projects, other, with a count of each. Show me five town page addresses as examples. Leave out any page named after a person.

Good: your balance and refill date, a map that cost 1 credit (every answer says what it cost in credits_consumed), and a count of your pages by kind that roughly matches what you know is on your site. Bad: Claude says it has no Context.dev tools, or the call comes back with a 401.

See “When it breaks”. Odd: pages you know exist are missing, or have no title. Context.dev builds the map from its index, and its docs say new pages can show up without titles for a while. The fix is in “When it breaks”.

When I ran this on our own company's site on 2026-10-12, it found 69 town pages, all for impact windows. Roofing had one county page and no town pages. That's the hole from the video. Your results will be your own.

The exact prompt: you vs a competitor

This is the one from the video. Two site maps at 1 credit each, and Claude does the sorting for free. Swap in your own site, the competitor and what you sell.

Which towns do they have pages for that I don't?

Two web-map calls, your site and theirs. Claude asks first, then sorts every page address by town and service.

Prompt: the comparison (2 credits) · lines 1-3 of 12. Copy all copies the whole prompt; read it in full on the page.

Which towns do they have pages for that we don't?

Use Context.dev's web-map. Our site: <yoursite.com>. Theirs: <theirsite.com>. What we sell: <service 1>, <service 2>, <service 3>.

Turn it into a build list

Free: no Context.dev call, just Claude working from what's already in the chat. This is the part that makes the first two credits worth it.

Prompt: the build list (free)

From the table, write my build list: the pages I'm missing, the most common gap first (for example, a service page in towns where I already have a town page). For each one: the town, the service and the page address I'd use, following my own site's pattern. Don't copy their titles or wording. No numbers that weren't in the maps. Put today's date at the top and call it a snapshot. In Claude Code, save it as a new file with today's date in the name.

Big site? Map just the town pages

Context.dev caps each answer at 40,000 characters, so a big site's map can come back cut short. Running the same map again gets the same cut and costs another credit. Filter it down instead.

Add a second competitor

Add a second competitor: <theirsite2.com>. Ask me first, map it with web-map (1 credit), and add a column for them under each service in the same table. Then tell me which gaps both competitors have covered and I haven't.

Check again next month

Map <yoursite.com> and <theirsite.com> again with web-map (ask me first: 2 credits). Compare with the build list file from <date>: pages they added, pages that are gone, and which of my missing pages I've built since.

What I got on 2026-10-12 (a snapshot, not a scoreboard): our own company had 69 town pages; the competitor had 25 towns. But they had a roofing page in 20 of those towns and an impact-door page in 23. We had no town-level roofing pages at all. They had 1 town we didn't, and 2 counties. The two maps cost 1 credit each.

What it costs

Checked 2026-10-12 on context.dev/pricing and claude.com/pricing. Context.dev also lists bigger plans (Growth, Scale, Enterprise) and says yearly billing saves two months. Unused credits normally don't roll over. On the free plan there's no overage: when credits run out, calls stop with 401 USAGE_EXCEEDED. Prices change: check before you buy.

From Context.dev's credits page, checked 2026-10-12. Every answer says what it cost (credits_consumed) and what's left (credits_remaining). A page-not-found (404) is billed at the base price. The two maps in my video cost 1 credit each.

Rough math for this whole guide: balance check 0, your site 1, the competitor 1, the table and the build list 0 (that's Claude, not Context.dev). That's 2 credits. On the free plan's 1,000 a month you'll run out of competitors long before you run out of credits. What eats credits is crawls, research answers and monitors, which is why the prompt keeps Claude off them unless you ask.

One catch on the free plan: one request at a time. That's fine here, since Claude runs the two maps one after the other.

When it breaks

The official docs behind every claim

• Context.dev
• Context.dev: Pricing
• Context.dev Docs: Install the MCP
• Context.dev Docs: Credits
• Context.dev Docs: Map
• Context.dev Docs: Map filters and search
• Context.dev API reference: Map
• Context.dev Docs: Rate limits
• Context.dev Docs: Troubleshooting

• Context.dev Docs: API keys
• Context.dev on Product Hunt
• Claude Code: MCP
• Claude Code: Advanced setup
• Claude Code: Memory (CLAUDE.md)
• Claude Help: Custom connectors
• Claude: Plans and pricing

What each page backs up is listed at the end of the full guide.

That's the setup

Two site maps, two credits, and every town page your competitor built that you didn't, sorted by service. Whether those pages actually rank is the next video; until then, my Manifold guide shows where a site ranks on Google.

Would you rather have someone build those pages on a site you own? That's our Custom SEO.

Want help setting this up? Receipts Group builds these systems.

Open the full guide as a page (every file in full, plus the table of contents).