Page Audit - Check a Page for SEO and GEO

The Page Audit checks a single page: you enter a keyword and a URL and get an evaluation for classic search engines (SEO) and for AI answers (GEO).

What does the Page Audit check?

The audit fetches your page live and gives it three scores:

Score Meaning
PageSpeed Technical loading performance, measured directly by Google
Meta Title, description, robots directives and other meta tags
Page quality Content and technical quality characteristics

Each score lies between 0 and 100. From 90 it counts as good, 70 to 89 is medium, below 70 is weak. The detail cards show where the numbers come from.

Start an analysis

  1. Open Page Audit in the navigation (or the home page)
  2. Enter the keyword the page should rank for, e.g. "web hosting"
  3. Enter the URL. Give the full address so the right page is checked, e.g. https://www.example.com/
  4. Click START

The analysis takes a few seconds and works without an account. You only need one when you want to save results, see the history in the dashboard, tick off recommendations and re-check them.

Tip: The keyword counts. Title, headings and content are measured by whether they fit the topic. If you want to check the same URL for several keywords, run a separate analysis for each.

The PageSpeed score arrives a little later

All other values are there immediately. Google measures the PageSpeed score and it follows in the background. Until then you see "Measuring PageSpeed at Google ...". This can take up to a minute, and the tile then fills in by itself. If Google couldn't evaluate the page, it says "PageSpeed score currently unavailable", and the best thing is to start the analysis again.

Reading the results

You can switch between Card View and List View.

The three scores

At the top, PageSpeed, Meta and page quality are shown as circle charts. The question mark next to the title explains what each score measures.

SEO cards

Card What is checked
Header HTTP status, redirects, content type, server, caching, size, SSL
DocType, Charset HTML5, page language, character set
Headings H1, H2, H3: present, unique, sensibly structured
Meta Tags Description, robots, viewport and more
Title Tag Present, length, keyword included
Content Amount of text and keyword distribution
Links Internal and external links
Images Alt texts, file size, format
Favicon Favicon present
Canonical Canonical tag set and matching
Strong Tags Emphasis in the text
CSS / JS files Number and kind of included files
Google TOP 3 Who currently leads for your keyword

Performance cards

The Core Web Vitals (loading time, responsiveness, visual stability) and the JavaScript, Resources and Network cards show where loading time is lost. The Core Web Vitals thresholds are in Understanding SEO analyses.

The AI card (GEO)

This one is about whether AI systems can read and cite your page at all:

  • llms.txt: does the file exist, is it valid, does it have sensible sections and links?
  • AI crawlers: does your robots.txt block known AI search and citation crawlers?
Careful: If you block the important AI crawlers in robots.txt, you will hardly show up in AI answers at all. So always take a look at this card.

Whether your brand is really named in AI answers isn't something the Page Audit measures. AI Visibility Tracking does that.

AI analysis

The AI analysis follows below the cards: a text with concrete improvement suggestions instead of raw numbers. How many AI analyses you can use, and with which AI model, depends on your plan.

Implementing recommendations

If you are signed in, every analysis is saved automatically. In the dashboard you open it in the detail view with the SEO Action Plan. All checks are sorted there into three groups:

Group Meaning
Critical Issues Fix these before anything else
Improvements Worthwhile optimizations
Passed This criterion is met

Each recommendation says how many points it costs ("pts"), why it matters and what the fix looks like, often with a code example. There are a few tools for working with them:

  • Copy code: puts the code example on the clipboard
  • Copy AI fix prompt: creates a ready-made prompt as Markdown that you can paste into your AI coding assistant
  • Mark as done: ticks off the recommendation, and the progress ("x of y completed") grows with it
  • Re-check: checks just this one criterion again without repeating the whole analysis, and reports "Issue fixed!" or "Issue still present". You can do that for a whole card as well.

Ticking off and re-checking only work when you're signed in. Some criteria can't be re-evaluated individually, those are only checked again in the next analysis.

Under Raw Data you find the unfiltered measured values for PageSpeed, Core Web Vitals, JavaScript, resources, network and header.

Device: mobile or desktop

Every saved analysis shows whether it was made for Mobile or Desktop. Rankings and loading times often differ a lot, so only compare analyses of the same device.

Status of an analysis

  • Running: the analysis isn't finished yet. Results and recommendations arrive as soon as it's done.
  • Incomplete: the analysis didn't run through completely. Missing values are not passed checks, so best run it again.

How to go about it

Enter URL and main keyword and start the analysis. Fix the critical issues first and then re-check whether they are gone. After that you work through the improvements, most points first. Don't forget GEO, so look at llms.txt and the AI crawlers. And in the dashboard you can see later whether the scores rise.

Frequently asked questions

Do I need an account?

No, the analysis works without one too. Saving, history, ticking off and re-checking only exist with an account, though.

How often should I analyze?

After every major change to technology, structure or content, otherwise roughly once a week. How many audits per week are possible depends on the plan.

Why do values differ between two analyses?

Either the page has changed, or Google measured PageSpeed differently. PageSpeed varies a little by nature, so look at the trend.

Can I check the whole website?

The Page Audit always checks one page. For the whole website you use the crawler.

Where does the data come from?

SEOFuxx fetches the on-page data live from your page, and the performance values come from the Google PageSpeed Insights API. robots.txt and llms.txt are read directly from your domain.

Is this content helpful?

·