Generate an hreflang implementation brief for a multi-region site
International SEO breaks down at the hreflang step — developers implement it wrong and SEOs struggle to write a brief that leaves nothing ambiguous. This prompt produces a precise implementation spec.
You are a technical SEO specialist. I need an hreflang implementation brief for a website with the following setup:
- Regions and languages served: {{REGIONS_AND_LANGUAGES}}
- URL structure used: {{URL_STRUCTURE}} (e.g. subdirectories like /en-gb/, subdomains like gb.site.com, or separate domains)
- CMS or platform: {{CMS_PLATFORM}}
1. Explain in one paragraph what hreflang does and the specific problem it solves for this site — written for a developer who has not worked on international SEO before.
2. Write the exact hreflang tag set for a sample page at {{SAMPLE_PAGE_URL}}, covering all regions listed above. Use correct ISO 639-1 language codes and ISO 3166-1 alpha-2 country codes.
3. List the 4 most common implementation mistakes for the URL structure I'm using, with a broken example and a corrected example for each.
4. Specify where the tags should be placed (HTML head, HTTP header, or XML sitemap) and explain when each method is appropriate.
5. Outline a QA checklist (5–7 checks) a developer can run after implementation to confirm it's working correctly.
Note: If the site serves the same language to multiple regions with no content differences, flag that hreflang may add complexity without clear benefit. {{REGIONS_AND_LANGUAGES}}{{URL_STRUCTURE}}{{CMS_PLATFORM}}{{SAMPLE_PAGE_URL}}
How to use this prompt
- Copy the prompt above (Copy button on the top-right).
- Replace each
{{VAR}}with your own value. Variables:{{REGIONS_AND_LANGUAGES}}{{URL_STRUCTURE}}{{CMS_PLATFORM}}{{SAMPLE_PAGE_URL}}. - Paste it into one of the recommended tools below.
- Iterate: tighten constraints in the prompt if the output is generic.
Why this prompt is structured this way
The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.
Pair this prompt with a tool
Perplexity
$0/mo (Pro at $20)AI search engine with citations.
Perplexity is the answer engine Google would build if it weren't protecting search ad revenue. Cited answers, follow-up questions, focused source modes.
Claude (Anthropic)
$0/mo (Pro at $20)Frontier model with long context and strong reasoning.
Claude (Opus / Sonnet / Haiku tiers) is the assistant favored by writers and engineers who care about reasoning quality and tone. 1M token context on Opus.
ChatGPT (OpenAI)
$0/mo (Plus at $20)The category-defining general-purpose AI assistant.
ChatGPT has the broadest feature surface: image gen, voice, custom GPTs, web browsing, code execution. Often the right default; sometimes beaten on specific tasks by Claude or Perplexity.
Jasper
$39/moEnterprise-grade marketing AI with brand-voice controls.
Jasper is built for marketing teams that need on-brand output at scale. Strong template library, decent brand-voice fine-tuning, plugs into Surfer for SEO.
The PlaybookPrompts weekly
One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.
Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.