Skip to main content
Reeve Consult

Check your website. Get your report.

Run a free SEO & AIO audit.

Enter your domain to check your website’s search foundations and get a PDF report of what to investigate.

  • No login
  • No email required
  • Download your PDF
What does the scan check?

The scan retrieves HTML from up to 20 accessible pages. It does not run JavaScript. Mobile and desktop performance tests cover the homepage; other findings concern the pages and resources included in the scan.

Get an automated report you can read, save and work through. The scan checks your website; it does not measure your Google rankings or whether an AI assistant recommends your business.

From scan to action

Your results, explained.

Review technical findings, page information and crawler access in one place. Save a PDF with affected URLs and an initial action plan to work through with your developer.

View the sample PDF
See what the audit checks
From website to next stepsIllustration
Your website
01
Collect evidenceAccess. Content. Signals.
02 / Review findings
See what needs
a closer look.
Page informationReview
Crawler settingsCheck
Search appearanceReview
03
Your action planKnow what to investigate first.
Evidence first. A clearer explanation. Practical next steps.

Start with the problem

Find the gaps between your website and the people who need it

Someone looking for your service needs to establish a few things quickly: whether you do the work, where you provide it, what happens next and how to contact you. A page that leaves these details unclear creates extra work for the visitor. Technical problems can make the same information harder for a search engine to access or interpret.

An audit gives you evidence to investigate. It is useful when you have launched a new website, changed platforms, added services or noticed that an important page receives little search traffic. It can also help you ask better questions when a developer or agency proposes changes.

01

Your service is difficult to identify

A generic page title or heading may say very little about the work you provide. Check whether a visitor arriving directly on that page can understand its subject without first visiting the homepage.

A clear service description gives that person a better basis for deciding whether to enquire.

02

The mobile journey feels awkward

Large images, shifting content or slow responses can interrupt someone trying to read a service page or complete a form. A performance measurement helps identify where to investigate; a real phone check shows how the journey feels.

Review the page and the task together, so a higher score does not become the only objective.

03

The information is inconsistent

An old address, an outdated service description or conflicting opening hours can leave people unsure which information to trust. Compare the visible page with the details used in structured data and business listings.

Keeping those facts aligned makes it easier for customers to act on accurate information.

Inside the audit

Understand what each check can tell you

The scan retrieves HTML from up to 20 accessible pages and runs mobile and desktop performance tests on the homepage. It cannot read content that appears only after JavaScript runs. Each finding needs context: an element that is missing on one page may be entirely appropriate on another.

01

Page titles, headings and descriptions

Titles and headings help describe a page. A report can flag missing or repeated values, but it cannot decide whether your description accurately reflects the service. Read the page alongside the finding: would someone understand the subject, the audience and the information available?

For example, three service pages with the title “Home” deserve a closer look. Giving each one a useful, accurate title helps distinguish the pages. Repeating a town or a keyword throughout every heading is not a substitute for explaining the work.

Your review: Compare the title, main heading and opening paragraph with the actual purpose of the page.

02

Crawling and indexing signals

A page may include a canonical URL, indexing instructions and links that affect how it is discovered or interpreted. A sitemap can help identify important URLs. These are useful technical signals to inspect after a redesign or migration, especially when an important service page seems to have disappeared from search.

The audit reports what it can observe from outside your website. Use Search Console to investigate Google's view of a particular URL and the indexing status of your pages. A successful visit by this audit does not prove Google has indexed the page.

Your review: Confirm the intended version of each important page and investigate unexpected noindex or canonical settings before changing them.

03

Performance on a phone

The homepage is submitted for mobile and desktop performance tests. Available lab measurements can help identify loading and rendering problems to investigate. Results can vary between runs because test conditions and the page responses vary. A lab result is not a pass for real visitor Core Web Vitals across the website.

Keep the customer's task in view. Open the page on a phone, read the service information, use the menu and try the enquiry route. A fast loading page still needs to be legible and usable.

Your review: Check the page's behaviour as well as the score. If the measurement is unavailable, treat it as not checked and investigate separately.

04

Structured data and business information

Structured data gives machines explicit information about a page and the things it describes. The useful question is whether the markup is appropriate, accurate and consistent with what people can read. A local business should not add unrelated schema types simply to collect more green ticks.

The scan can identify the markup it finds. Its presence alone does not prove that every property is valid or that a search feature will appear. Review relevant markup with a validation tool and check that names, contact details and service descriptions match the visible page.

Your review: Use the correct type for the page. Keep the facts accurate, and validate the implementation.

05

Crawler preferences for search and AI services

Different crawlers serve different purposes. A robots.txt rule can express a preference for one named crawler without applying to every search engine or AI service. Before changing a rule, establish which service it concerns and whether the restriction was deliberate.

The report can surface relevant directives for review. It cannot confirm every crawler's real visit or establish that a firewall, CDN or hosting rule will let a particular service through. Server logs and the provider's own tools may be needed to investigate actual access.

Your review: Separate search access, user requested retrieval and model training policies. They are different decisions.

06

Images and supporting page information

Image alternatives and sharing metadata contribute to how a page is understood in different situations. A missing alternative can be worth investigating when the image carries information. A purely decorative image may correctly use an empty alternative.

Likewise, a word count is a description of the retrieved page, not a target that every page must exceed. An accurate contact page can be short. A complex service may need much more explanation. Use the finding to review the information a person needs to complete their task.

Your review: Describe useful images appropriately and add content where it answers a real question.

Read the evidence

Use the findings to plan practical improvements

The score summarises the checks in this report. It is not a Google score, a forecast of traffic or a percentage chance of being cited by AI. Read the findings behind it before deciding what to change.

Start with anything that conflicts with the intended behaviour of an important page. An accidental instruction to exclude a live service page is different from a deliberate instruction on a private or duplicate page. Priorities also depend on the pages your customers use, the work required and the risk of changing the website.

Passed
The automated check completed and did not flag an issue under its stated rules.
Review
The tool found something that needs an explanation or a check against the page's purpose.
Not checked
A measurement or resource was unavailable, or the check was outside this scan's scope. This is not evidence that the page failed.
Information
Context or an optional item that may help your review without establishing an error.
  1. 01

    Confirm the finding

    Open the affected page and check the evidence. Record what should happen and why the current behaviour appears wrong.

  2. 02

    Agree the change

    Give the responsible person the URL, the finding and the intended result. Ask whether a shared template or setting affects other pages.

  3. 03

    Verify the result

    Check the published page and the customer journey after the change. Run the relevant check again and retain the original report for comparison.

  4. 04

    Measure what follows

    Review search activity and completed enquiries over a suitable period. A changed audit score does not, by itself, demonstrate a change in search performance.

Illustrative examples

Turn a flagged finding into a useful investigation

These examples show how someone could use an audit. They describe invented situations, not customer results or promises of improved rankings.

Example 01 / Illustrative

Several service pages have the same title

An electrical contractor has separate pages for inspections, rewiring and commercial maintenance. Each uses the same page title: “Welcome | Example Electrical”.

Why investigate
The title does little to distinguish the pages. Someone comparing search results may need more information to identify the service they want.
What to check
Read each page and choose a precise title that reflects its subject. Check whether the repeated value comes from a shared website template before editing the pages individually.
How to verify
Confirm the published titles and rerun the duplicate check. Use Search Console to review the relevant pages over time; the title change alone does not establish why traffic moves.
Example 02 / Illustrative

An important live page contains noindex

A business launches a new service page after testing it in a preview environment. The published page still includes an instruction asking search engines not to index it.

Why investigate
If the instruction is unintended, it conflicts with the business's aim of making the page discoverable through search.
What to check
Confirm that the live page should be public and indexed. Ask the developer to check the source of the instruction and whether it also affects other pages or appears in an HTTP header.
How to verify
Inspect the published response after the change and use Google's URL Inspection tool. Indexing can take time and is not guaranteed.
Example 03 / Illustrative

A mobile performance measurement is unavailable

The audit retrieves the site but the external performance service does not return a usable measurement.

Why investigate
There is not enough evidence to call the page fast or slow. Giving it a zero would make an unavailable test look like a measured failure.
What to check
Read the availability note, try a separate performance test and check the page on a phone. If the problem persists, investigate the response from the measurement service and the site's access rules.
How to verify
Record a valid test result when available. Keep a note of the date and test conditions when comparing later runs.

Your audit report

Keep the evidence with the work you need to do

The PDF gives you a record of the scan to save or share with the person looking after your website. Use it to agree which findings are relevant, who will investigate them and how you will check the changes.

A useful handover includes the affected URL, the evidence, the intended outcome and a way to verify the work. For example, “review these three repeated titles” is easier to act on than “improve SEO”. Keep the report with any notes about deliberate settings or tests that could not complete.

  • The audited website and scan date
  • The pages included in the scan
  • Category results and the findings behind them
  • Recommendations to investigate
  • Scope and unavailable measurements

Illustrative data. The sample is not an audit of your website.

Reeve Consult
Website review / Sample reportSEO & AIO
website audit.

Understand the findings.
Choose your next steps.

Your website.
A clearer way forward.
Website audit01 / Summary
Start with the evidenceFindings into
priorities.

A summary of the checks, with detail to help you investigate.

Technical SEODetails →
On-page informationDetails →
Content structureDetails →
External referenceDetails →
Search crawler accessDetails →
01

What to investigate firstEvidence · explanation · next step

Sample report design. Your report contains the findings available from your scan.

After the scan

Choose the work that helps your customers use the website

You may be able to correct an outdated description or contact detail yourself. Template settings, performance issues and indexing instructions may need a developer. Start by separating factual corrections from technical changes and larger decisions about your content.

If you would like Reeve Consult to help, tell us which website and pages you are concerned about, the findings you want to understand and what visitors need to be able to do. We can discuss the evidence, the intended customer journey and the work involved before you decide how to proceed.

Your questions

More detail before you run an audit.

What is an SEO and AIO audit?

It is a review of website information and technical settings relevant to discovery and use. This tool produces automated findings from the pages and resources it can access. It does not establish where you rank in Google or whether an AI service mentions your business.

Does this audit check every page on my website?

No. It retrieves HTML from up to 20 accessible pages, starting at your homepage. It does not run JavaScript. Performance tests concern the homepage. Read the pages and measurements included in your report; a sample audit is not a complete crawl of a large website.

Can a high score guarantee better rankings or AI citations?

No. The score reflects this tool's checks and scoring method. It does not measure the quality of every customer journey, every ranking factor or an AI system's choice of sources. Use the findings alongside your website, Search Console data and relevant business goals.

Do I need llms.txt or special AI schema?

Google says neither special AI files nor special schema are required for AI Overviews or AI Mode. Treat llms.txt as optional. Add structured data when it accurately describes the page and supports an appropriate use, rather than adding types simply to improve an audit score.

Does blocking Google-Extended block Google Search?

No. Google-Extended is separate from Googlebot's Search controls. Check which product a rule concerns and whether it expresses a deliberate policy before changing it.

Why does the report say a check was not completed?

A website resource or external measurement may be unavailable, restricted or outside the scan's scope. That result is a gap in the evidence. Check the note, investigate separately if the measurement matters, and do not treat an unavailable test as a measured failure.

Will the audit change my website?

No. Running the scan does not edit your pages or settings. Review recommendations before making changes, especially where the current behaviour may be deliberate.

Can I use it with a WordPress, Shopify or custom website?

The tool retrieves publicly accessible HTML rather than requiring a particular website plugin. It can be used with different website platforms, but it does not run JavaScript. Access restrictions and content that appears only after JavaScript runs can limit the findings.

How often should I run an audit?

Run a relevant check after a significant change, such as a redesign, migration or template update, and again when you have published corrections. Keep dated reports so you can compare the same pages and understand which measurements have changed.

Is this connected to the AIOSEO WordPress plugin?

No. This is Reeve Consult's website audit. In this page, AIO refers to optimisation for AI search experiences. AIOSEO is a separate WordPress product.

Reeve Consult

Put your website findings into context.

Tell us what your website needs to do for the business and which findings you want to understand. We can discuss the evidence and the work involved before you decide what to change.

Explore our web development service

Discuss the findings

Your PDF download is separate from this enquiry. No report is automatically emailed.