seo-geo-optimizer

seo-geo-optimizer

Purpose

Optimize a website for both traditional search engines and AI search engines: improve rankings, increase qualified traffic, strengthen topical authority in the venture's domain, and make content easy to cite in AI-generated answers.

Strategic objective

Every recommendation supports at least one of: rank for high-intent queries; capture qualified demand from the target audience's search intent; improve AI-citation likelihood through structured, factual, extractable content; build topical authority across the venture's core topics; and push readers toward the primary conversion path. Optimize through the venture's positioning and audience as defined in market-profile.md.

Core workflow

Step 1 — Map keyword strategy

Assign intent and keyword targets before editing any page.

• Build keyword clusters centered on real business intent — a set of primary clusters (core commercial phrases) and secondary clusters (specific, long-tail, comparison, and process terms). Derive them from the venture's offer and audience.
• One primary intent per page: one dominant keyword theme + a small set of related secondary terms; don't target the same core phrase on multiple pages without clear differentiation; separate transactional from informational intent. Service pages target commercial/transactional queries; resource pages target educational/comparison queries; multilingual versions support the same intent without duplication confusion.
• Evaluate keyword fit: does the page satisfy the exact intent, avoid being too broad, include detail that makes it uniquely valuable, and attract qualified users (not just traffic)?

Step 2 — Site architecture & multilingual URL structure

• Clean, predictable URLs grouped by intent (commercial pillars, /resources/ hubs, and a dedicated language section such as //resources/).
• Multilingual rules: keep language organization explicit; group each language under a predictable section; link language equivalents; use hreflang when versions target distinct language users; handle duplicate content across languages with correct canonical + hreflang.
• Goals: commercial pages easy to find and rank; resource hubs build authority; article traffic routes back to service/lead pages; structure scales to new languages without URL chaos.

Step 3 — Page-level SEO

• Title tags: pattern [Primary Keyword] | [Brand] — [one-line positioning]; keyword near the front; commercially clear; tailored to page intent, not one template everywhere.
• Meta descriptions: expand the commercial value, state the concrete benefit, align tightly with intent, encourage clicks without filler.
• Headings: one clear H1 on the core topic; H2s matching the main sub-intents; H3s only for genuine deeper breakdowns; specific enough to support scanning and AI extraction.
• Intro sections: a direct answer/definition in plain language, why it matters commercially, and what the user can do next.

Step 4 — GEO-ready content (AI citations)

Each important page should include: a clear definition near the top; a numbered process for workflows; specific data points where available; short standalone factual sentences; FAQ blocks matching real questions; and a trust-oriented explanation of how the venture resolves the uncertainty. AI-citation checklist: a concise directly-quotable answer; specific named entities/terms relevant to the domain; unambiguous structured headings; FAQ language matching how users actually ask in search and chat. Style: specific, factual, non-fluffy, easy to summarize; no long generic intro before the answer.

Step 5 — Topical authority

• Pillar themes: the venture's core authority areas (offer, cost/pricing breakdowns, verification/due-diligence, process guides, category guides, documentation/terms, and audience-education resources).
• Content-hub logic: service pages as commercial pillars; /resources/ (and per-language hubs) as authority hubs; supporting articles answering sub-questions, each linking back to a service or conversion page; refresh evergreen content as new information appears.
• Content-gap analysis: look for missing category guides, verification checklists, cost/estimate explainers, per-language versions of high-intent content, and FAQ-driven pages from recurring audience questions.

Step 6 — Internal linking

Link resource/blog content back to the conversion page; link articles to the most relevant service page with descriptive anchor text; link service pages to trust-building resources; avoid "click here"; keep paths commercially logical and user-first.

Step 7 — Structured-data schema

• FAQPage — when real visible FAQs exist; concise direct answers matched to real demand; text visible on-page.
• HowTo — for process pages; clear ordered steps mirrored in the page body; avoid when the page is abstract/advisory.
• LocalBusiness — for the business-entity pages (homepage/identity); accurate name, site, contact, and service context, consistent with visible info.
• Service — on service pages; describe the service clearly, align type with page intent, include geographic relevance where appropriate; avoid vague labels.

Step 8 — Conversion alignment

Ensure each page has a CTA matched to its intent; route informational readers toward the conversion path; match CTAs to user readiness (estimate request vs verification vs demo); never leave a ranking page with no clear next step.

Step 9 — Output format

Deliver as: objective; target keyword cluster; recommended page/content updates; title-tag + meta-description recommendations; schema recommendations; internal-linking plan; GEO enhancements for AI citation; CTA alignment.

Writing rules

Be precise and commercially useful. Tie every recommendation to traffic quality, rankings, AI-citation potential, or conversion. Favor concrete rewrites over vague optimization advice. Keep multilingual recommendations structured and intentional.

Do not

• Do not suggest generic content unrelated to the venture's actual audience and domain.
• Do not treat SEO and GEO as unrelated systems.
• Do not recommend keyword stuffing.
• Do not publish pages that build traffic but support no conversion.
• Do not ignore secondary-language structure when planning multilingual growth.

Quality standard

A strong output makes it immediately clear which keyword cluster each page should own, how title tags and meta descriptions should read, which schema types go where, how multilingual URLs should be structured, what makes the content citable by AI search, and how visibility connects back to conversion.