Reading your audit report

Every audit lands you on a screen with three tabs and a Retest button. Everything here is written for a non-technical site owner — no SEO jargon without its plain meaning.

The three buckets

• Fix now — problems Google reacts to fastest. Every row is either critical or a broken signal you can act on today.
• Watch — smaller issues, or checks where we did not have enough data to score. Worth tracking, not usually worth stopping the world.
• Passed — checks your site cleared. Reviewing this tab occasionally is a good sanity check.

Anatomy of an issue

Each row shows:

• Title — a plain-language name for the problem.
• Why it matters — one sentence on why Google or a real visitor cares.
• Where — the exact URL(s) affected, so you can jump straight there.
• Exact fix — the concrete change to make. A copy button puts the fix on your clipboard.

Retest and diff badges

Click Retest after you have shipped a fix. The next audit compares against the last one and shows two badges on each row:

• Fixed — the rule that used to fail now passes on that URL.
• Regressed — the rule newly failed on a URL. New failures also count as regressions.

Diffs are taken against the frozen snapshot of your previous audit, so what you saw yesterday will still say the same thing tomorrow.

llms.txt

A /llms.txt file is an emerging convention: a plain-text pointer file that lets AI assistants (ChatGPT, Perplexity, Claude, and others) know which of your pages are safe to cite and preferred. RankMeFast treats this rule as advisory — we suggest adding one, but nothing is broken if you have not.

Every rule in plain words

• Blocked from Google — A robots.txt rule is telling Google to stay away. If the page should rank, remove the disallow line.
• Sitemap missing or weak — A sitemap is a file at /sitemap.xml that lists your pages. Add one and reference it from robots.txt.
• Page titles missing or weak — The <title> element decides your Google click bait. Aim for a specific, 30–60 character title on every page.
• Meta descriptions missing or duplicated — The one-line snippet Google shows below the title. Write a unique description per page.
• Page headings missing or overused — One <h1> per page, then <h2> / <h3> for structure. Missing <h1> is a big deal; two <h1>s is a smaller one.
• Canonical link missing or broken — A <link rel="canonical"> tells Google which URL is the "real" one. Missing or pointing off-site is bad.
• Structured data missing or broken — Machine-readable tags (JSON-LD) that help Google understand articles, products, FAQs.
• Broken internal links — Links from one of your pages to another that return an error. Fix or remove them.
• Thin content — Pages with fewer than ~200 words look empty to Google. Expand the ones that should rank.
• No FAQ signals found — No question-and-answer sections detected. FAQs help both users and AI assistants.
• llms.txt file missing (advisory) — An emerging convention: a /llms.txt file that hints AI crawlers about your best content. Not required — advisory only.
• HTTPS not enforced — Your site should redirect http → https and canonicalise the https version.
• Poor real-visitor performance — Real visitors experienced a slow page. Data comes from Google’s Chrome UX Report — sites with little traffic may have none of it yet.
• Low lab performance estimate — Our synthetic Lighthouse run scored low. A single run varies ~10 points; treat as a hint, not a verdict.
• Not mobile-friendly — Phones do not render the page well. Check tap-target sizes and the viewport meta tag.
• Not indexed by Google — Google looked at the page but did not add it to search. Reconnect Google Search Console if this rule cannot fetch data.
• Rich results issues — Structured data was recognised, but Google flagged errors that block enhanced search results.
• Indexed with warnings — The page is indexed but Google flagged a canonicalization or duplicate-content signal.

Back to the docs index