agentleFS
coolxeocoolxeo/grok-bot-skills/skills/seo/exact-match-intent-seo/SKILL.md

exact-match-intent-seo

Skill8 starsChanged 3 days agoMITView on GitHub

use this when choosing domains, URL slugs, titles, or H1s for SEO — Exact Match Domain (EMD) lessons and the safer brand-domain equivalent

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Prefer exact-match paths on a brand domain (/easy-weeknight-recipes) over buying a spammy EMD for every keyword.

    line 28
  2. Distinctive:

    Write titles for CTR: clear, specific, honest.

    line 29
  3. Distinctive:

    After indexation, use Search Console: queries with impressions but weak copy get the phrase into H2 / body / alt (refresh, don’t spam).

    line 31
  4. Distinctive:

    Keep one indexable page per intent.

    line 32
  5. Distinctive:

    Treat a GSC flex video as a full playbook when it only shows metrics + music.

    line 39
  6. Distinctive:

    Only for a new niche property where the whole site is that one intent, content depth is real, and you are not splitting brand authority.

    line 43
  7. Distinctive:

    Run alongside AEO GEO site for structure, schema, and trust.

    line 58

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Exact-match intent SEO (EMD lesson)

Triggered by posts that credit EMD SEO (Exact Match Domain) for high CTR on new sites — e.g. Hridoy Reh showing ~8.9k clicks / 27.3k impressions / 32.7% CTR / avg position 2.8 after months of near-zero.

What the claim usually means

An Exact Match Domain is a domain whose name equals the target query (e.g. easy-weeknight-recipes.com). Classic SEO used EMDs as a ranking shortcut. In 2026 that boost is weak or gone as a direct factor; what still works is exact intent match across:

  • Domain or path (slug)
  • Title tag
  • H1
  • Opening copy
  • SERP snippet (high CTR when query ≈ title)

High CTR + top-3 average position usually means the result looks like the answer to a specific query, not a broad brand homepage.

Do / don't

Do (brand sites and new niches)

  1. One primary intent per page. Name it in the slug, H1, and title the same way searchers type it.
  2. Prefer exact-match paths on a brand domain (/easy-weeknight-recipes) over buying a spammy EMD for every keyword.
  3. Write titles for CTR: clear, specific, honest. Avoid bait that the page does not pay off.
  4. Expect a sandbox / lag: months of near-zero impressions, then a sharp climb. Do not kill pages early without a GSC read.
  5. After indexation, use Search Console: queries with impressions but weak copy get the phrase into H2 / body / alt (refresh, don’t spam).
  6. Keep one indexable page per intent. Do not duplicate the same keyword across many thin URLs.

Don't

  • Buy a keyword EMD and ship thin affiliate pages. Google still demotes low-quality EMDs.
  • Over-repeat the domain keyword in every title and heading (over-optimization).
  • Replace a working brand domain with a string of EMDs for the same product.
  • Treat a GSC flex video as a full playbook when it only shows metrics + music.

When an EMD is worth considering

Only for a new niche property where the whole site is that one intent, content depth is real, and you are not splitting brand authority. Microsite, not the main brand door. Default for an established brand: stay on the brand domain and use exact-match slugs.

Checklist before shipping an intent page

  • Primary query written in plain words
  • Slug matches that query (kebab-case)
  • Single H1 matches intent (not a clever brand-only line unless brand is the query)
  • Title ≈ H1, under ~60 chars when possible, no false claims
  • First paragraph answers who / what / what next
  • Unique from other pages (no near-duplicates)
  • In sitemap if indexable; noindex only for experiments
  • After 4–8 weeks: GSC query report → refresh for “impressions, not in copy”

Pair with

Run alongside AEO GEO site for structure, schema, and trust. Exact-match intent is the SEO/CTR slice; AEO/GEO is the AI-citability slice.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.