SEO + AEO + GEO Home Page Audit

The title is the strongest single on-page relevance signal and the line a searcher actually reads. Titles that are missing, truncated, or identical across pages either get rewritten by Google or lose the click to a clearer result.

1. Write down the single query this page should win, in the words a searcher types.
2. Front-load the distinguishing words — the first 30 characters survive every truncation.

Google rewrites missing or generic descriptions from arbitrary page text, and the rewritten snippet is usually worse than one written deliberately. A specific description controls the pitch and measurably lifts click-through from the same ranking position.

1. State what the page gives the searcher in one or two sentences — the output, not the topic.
2. Include the specifics a rewrite would lose: numbers, audience, the concrete promise.

Schema makes the page eligible for rich results — FAQ dropdowns, breadcrumbs, article treatments — which raise click-through from the same position. It also removes ambiguity about what the page is and who published it.

1. Pick the type that matches the page: Article for editorial, FAQPage for a genuine Q&A block, HowTo for numbered steps, WebApplication for a tool.
2. Emit it as JSON-LD in the head, with name, description, author, publisher and dates.

Generative engines lift whole passages. The paragraph that reads correctly with no surrounding context is the one that gets quoted verbatim.

1. Put the answer immediately after the H1, before any form, tabs or hero imagery.
2. Name the subject explicitly in the first clause — never open with 'This tool' or 'It'.

Short, stat-bearing bullets are the single most-quoted element in AI answers, because each one is already a complete claim.

1. Place three to five bullets directly under the quick answer.
2. Write each as one full sentence that is true in isolation — no 'as above' or 'this'.

A heading matching the prompt wording gives the engine an unambiguous passage boundary, and question headings are what FAQ and passage extraction key on.

1. Replace label-style headings ('Overview', 'Details') with the question the section answers.
2. Use the wording a person would type, not internal jargon.

Schema does not force a citation, but it removes ambiguity about what the page is, who wrote it and who published it — and mismatched schema is worse than none.

1. Pick the type that matches the page: Article or Posting for editorial, HowTo for procedures, FAQPage for Q&A, WebApplication for tools.
2. Include author, publisher, datePublished, dateModified and mainEntityOfPage.

Engines lean hard on resolvable authorship when deciding whose claim to repeat. A byline with nowhere to click is treated as anonymous.

1. Add a visible byline near the top or bottom: name, role, organisation.
2. Create a real profile page with credentials, subject areas and contact route.

llms.txt is the emerging plain-text map of what a site covers. A bare link list is better than nothing, but a one-line summary per URL is what actually gets a page selected.

1. Generate /llms.txt from the same data source as your sitemap so it can never drift.
2. Open with an H1 for the site and a one-paragraph description of what you publish.