Skip to main content
Evidence-first SEO + GEO audit

Make your website easier for search and AI to understand

Audit public sites with bounded page sampling, factual SEO/GEO checks, PageSpeed data, and evidence-linked fixes. Predictions are shown separately and never change the factual score.

⚙️
Factual SEO
Indexability, metadata, structure, schema and performance
🤖
GEO readiness
Entity clarity, extractability, authorship and source support
🏛️
Evidence first
Every action names the page, observation, fix and re-check

· No advertising profiles · No account needed · MIT open source

Custom API

Optional. Use a compatible API once after the factual audit to build query and answer evidence. It never changes the factual score.

The three fields are cleared before the audit starts and are never written to browser storage, the URL, or reports.

Try:

GeoScore at a glance

Live product facts come from the deployed API.

Version
...
Site sample
...
Audit modes
...
Check registry
...
Optional modules
...
Fresh-audit limit
...
License
MIT
Source
GitHub

Loading live product facts...

Scope and data sources

GeoScore audits public HTTP(S) sites. Private networks, IP literals, credentials and custom ports are rejected.

Bounded public fetches

Site mode samples the homepage, About page and representative internal pages. URL mode audits the target and may read the homepage for context.

Optional evidence sources

PageSpeed, CrUX, W3C Nu, Common Crawl, DNS, certificate logs and other public APIs can add evidence. Provider failure is reported as unknown or error, not as a penalty.

Informational, not professional advice

Results are SEO/GEO signals, not legal, financial, compliance, penetration-testing or professional security conclusions.

What GeoScore checks

Known, applicable factual checks determine readiness scores. Unknown, error and not-applicable states do not reduce them.

Indexability and discovery

robots.txt, sitemap discovery, canonical URLs, noindex directives and public fetch status.

Page semantics

Titles, descriptions, headings, language, links, images and cross-page consistency.

Schema fit

JSON-LD presence is separated from whether a schema type fits the detected site and page type.

Factual GEO readiness

Entity and author consistency, direct answers, extractability, claim/source support, statistic provenance and freshness.

Performance evidence

PageSpeed lab data and CrUX field data retain source, status and partial-failure details.

Predicted visibility

AI simulations are clearly labelled Predicted, carry zero scoring weight and are not presented as real citations.

SEO and GEO work together

Search and answer systems both need crawlable pages, clear entities, extractable answers and well-supported claims. GeoScore turns those observable signals into a prioritized repair list without inventing business facts.

What the report includes

  • ?Site profile and confidence before scores
  • ?The sampled pages and evidence source for each finding
  • ?Three priority actions on screen, plus every failed check in one Markdown repair report
  • ?Per-item AI fix packs remain optional advanced details for recorded failures

Frequently asked questions

Short answers about scoring, predictions, privacy and limits.

Is GeoScore free?
Yes. The public service uses fair-use limits for fresh audits. Cached report views do not consume the fresh-audit quota.
Does GeoScore monitor real AI citations?
No. It audits factual SEO/GEO readiness and may show a separate Predicted simulation. It does not claim to observe live citations from third-party answer engines.
How are scores calculated?
Known, applicable pass/fail checks form the raw weighted score. Critical, major and minor failures cap a category at 49, 79 and 94; incomplete coverage or confidence can lower it further. Evidence below the minimum returns no overall score.
Which language does the report use?
The product follows your saved UI language. The report defaults to the audited page language and has its own saved English/Chinese switch.
What data is stored?
GeoScore stores public audit results and operational rate-limit/cache data. Do not submit confidential or private URLs.
Can it audit localhost or private networks?
No. Only public domain hostnames and public HTTP(S) URLs are accepted.