Intelligence module

Whether search engines can find your pages, read them and work out what they are for

Three separate questions, frequently confused, and a site can fail any one of them while passing the other two.

Search engine optimisation has acquired a reputation for mystery that the underlying mechanics do not deserve. A search engine has to reach your page, retrieve its content, understand what the page is about, decide whether to keep it, and then judge it against everything else it holds on the same subject.

Each of those steps can fail, and they fail for different reasons. Reaching can fail because of directives, architecture or errors. Understanding can fail because a page never states plainly what it is about. Judging can fail because five of your pages make the same claim and none of them is clearly the authority.

This module works through those steps in order and reports where the chain breaks, because a failure early on makes everything downstream irrelevant.

Scope

What is examined

All of it established deterministically from what your server returns. Nothing here is inferred from third-party estimates.

Discovery

robots.txt reachability and directive interpretation
Sitemap availability, validity and correspondence with the site
Internal link structure and what it reaches
Response status across the pages examined
Redirect behaviour, including chains and loops

Indexation control

Indexing directives in markup and headers
Canonical declarations and whether they are self-consistent
Conflicts between what different signals instruct
Pages excluded deliberately against pages excluded by accident

Page-level signals

Titles: presence, length, distinctiveness and specificity
Meta descriptions: presence, length and whether they describe the page
Heading hierarchy and whether it reflects document structure
Content volume relative to the page's commercial purpose
Image alternative text where it carries meaning

Site-level relationships

Whether multiple pages compete for the same intent
How internal linking distributes emphasis
Whether the architecture communicates a hierarchy
Consistency of naming across comparable pages

Machine-readable meaning

Structured data types present and their validity
Whether markup corresponds to visible page content
Organisation and service definitions
Language and regional declarations where applicable

Serving quality

Whether content is present without JavaScript execution
Response times observed during the fetch
Performance measurement via PageSpeed Insights
Mobile presentation of the pages examined

A page that cannot be reached does not benefit from being excellent. The order in which these things are checked is the order in which they should be fixed.

Interpretation

What the score reflects

Reflects how completely and consistently the website presents the signals search engines rely on to crawl, interpret and evaluate its pages.

It does not reflect your rankings, your traffic, or how much revenue search generates for you. Those are outcomes, determined partly by these signals and largely by demand, competition and what you actually sell. A site can score 88 and earn very little traffic because nobody is searching for what it offers.

What the score is useful for is comparison over time and identification of where effort would help. A technical score that rises from 61 to 84 after a quarter of work is evidence the work was done properly, whatever the traffic did in the same period.

Commonly surfaced

Titles that name the organisation before the subject
Several pages competing for one commercial intent
Canonical declarations pointing somewhere unintended
A sitemap listing addresses that redirect or error
Important pages reachable only through the footer
Content that requires JavaScript to appear at all
Structured data describing something not on the page
Heading structure used for appearance rather than meaning

Example finding

A representative finding

This is an illustration of the report format rather than a result from a real assessment.

Moderate

Page Titles Lead With The Company Name

What we found: Every title examined begins with the organisation's name, followed by a separator and then a short description of the page. On several pages the descriptive portion is truncated in search results because the prefix consumes the available width.
Why it matters: The opening words of a title carry the most weight, both for search engines determining relevance and for people scanning results. Leading with a name that the reader may not recognise spends that position on the least useful information, and on longer titles it pushes the subject out of view entirely.
General direction: Lead with what the page is about and place the organisation name at the end, or omit it on pages where it adds nothing. Keep titles within a length that displays fully, and make sure each is distinguishable from the others at a glance.
How IXSEO can help: SEO Audit, or Technical SEO for template-level changes.

Frequently asked questions

Does this tell me what I rank for?

No. Ranking data comes from Search Console, which reports what your site actually earns and is the authoritative source. This module examines something different — whether the signals search engines rely on are present, consistent and unambiguous. A site can rank adequately with poor signals and would rank better without that handicap.

How does this differ from a Lighthouse SEO score?

Lighthouse checks around a dozen mechanical conditions on a single page and reports whether each passes. That is useful and nowhere near sufficient. This module examines relationships across pages, consistency between declarations, whether the architecture communicates a hierarchy, and whether what a page claims to be matches what it contains.

Why does the module flag things my current agency says are fine?

Sometimes because they are fine and the finding is noise, which is why every finding carries a confidence level and an explanation you can argue with. Sometimes because a signal that was harmless in isolation becomes a problem in combination with something else on a different part of the site. Bring the report to them; a good agency will engage with the specifics.

Is keyword research part of this?

Not in the automated assessment, which works from what the site publishes rather than from what people search for. Demand analysis forms part of a strategy engagement, where it belongs alongside a conversation about what the business actually wants to sell.

ServiceSEO AuditThe full engagement, with human review and prioritisation.ModuleTechnical HealthThe delivery layer beneath these signals, examined in its own right.ModuleGEOThe same website, assessed for how generative systems read it.

Run the SEO module on your website

It is selected by default on the free snapshot, alongside GEO, Content and Technical Health.

Analyse your website Discuss an audit