Measure SEO, AEO and GEO from search visibility to useful enquiries

What our own site check taught us

In our 5 October 2026 check, the public Woro sitemaps contained 350 and 27 URLs without duplicate entries. A sample of 18 pages had a single main heading, the expected canonical address and no page-level indexing block. That did not prove indexing or analytics receipt. A separate inspection found our Google command queue used ordinary arrays instead of the documented Arguments objects. The earlier consent checks used stand-ins and had missed that difference. The lesson was to validate the actual measurement contract and dashboard receipt before interpreting zero traffic as zero interest.

Record the baseline before making changes

List your priority service pages, the buyer question each answers and its intended next action. Record indexing status, search impressions, clicks and the time period. Note whether the data covers a domain property or a URL prefix. Keep branded searches separate from broader service searches so increased interest in your company is not mistaken for a new category ranking.

Inspect the page behind the number

A page can be accessible to a visitor without being indexed. Inspect representative URLs and read the actual exclusion reason before adding more articles. Check the response, canonical URL, internal links and robots controls. A sitemap submission helps discovery, but does not establish indexing or a particular search position.

Explain the analytics coverage

A site using basic opt-in measurement does not record every visitor through Google Analytics. Rejected consent, browser restrictions and blockers affect the observed dataset. Keep these limitations in reports. Do not treat a difference between server requests and analytics sessions as a precise count of lost customers; automated requests and repeat visits can also differ.

Connect useful visits to an enquiry

Define a useful enquiry with the team receiving it: relevant service, usable contact details and enough information to continue. Record the source when it is available and appropriate. Keep test enquiries separate. A button click is an expression of intent; it is not the same as a successfully received form or a qualified opportunity.

Treat AI mentions as observations

For AEO and GEO, record the question, system, date, answer and cited source. Check whether the business facts are right. Repeating the same prompt is a sampling exercise, not a controlled ranking test. Google’s current guidance also describes Search Console inclusion controls for its generative AI features; verify the property setting rather than assuming it.

Review changes on a useful cadence

Compare similar periods and record campaigns, seasonal effects and publishing changes. Keep the pages that answer distinct buyer questions and improve pages whose visitors cannot find the next step. Woro Global can scope the content, site and measurement work together; the baseline and acceptance criteria should be agreed before making performance claims.

Sources and further reading

• Google: Search performance report
• Google: generative AI search guidance
• Google: basic and advanced consent mode

Discuss your workflow

Explore the service or prepare a project brief. Scope and verification depend on your systems and requirements.