Page auditing
How GEOrgina audits a webpage
GEOrgina reads a live URL and scores it against deterministic Generative Engine Optimisation checks, then links every finding to the roadmap task that fixes it.
What is a GEO page audit?
A GEO page audit is an assessment of how well a single live page can be retrieved, understood, trusted and cited by AI answer engines. It is not a performance or accessibility report: it examines the signals a language model relies on when it decides whether a page is a usable source for a generated answer.
How does GEOrgina audit a webpage?
The partner pastes a public URL into the audit tab, or simply sends the URL to GEOrgina in chat. GEOrgina fetches the served HTML, runs a fixed set of deterministic checks, weights them into a score out of 100 and writes a short verdict in the partner's language. Because the checks are deterministic, the same page produces the same score, so progress between audits is comparable.
What does GEOrgina check on a page?
Machine readability: a single clear H1, a logical heading hierarchy, semantic HTML, a title and meta description, and text that exists in the served HTML rather than only after JavaScript runs.
Entity and trust signals: structured data, a clear statement of who the organisation is, authorship, contact and identity signals, and consistency between the visible copy and the structured data.
Answerability: question-shaped headings, direct answers in the first paragraph under each heading, self-contained sentences that still make sense when extracted, and factual specifics rather than marketing language.
AI-engine crawlability: a canonical URL, indexable robots directives, a reachable robots.txt and sitemap, internal links into the page and no blocking of the user agents AI search engines use.
What does a partner get from an audit?
A score out of 100, a category breakdown, an ordered list of findings with the reason each one matters, and a link from each finding to the roadmap task that resolves it. Every audit is stored, so a partner can re-audit the same URL after shipping a fix and see the difference.
What happens with JavaScript-heavy pages?
If the important content only appears after client-side rendering, GEOrgina flags it, because an AI engine that reads the served HTML may never see that text. That flag is usually the single highest-impact finding on a page, and it is the reason the GEOrgina public website is itself server rendered.