Reading your audit report

After each audit you land on a report with three tabs and a Retest button. It's written for site owners rather than SEO specialists, and any technical term comes with a plain explanation.

The three tabs

• Fix now: problems Google reacts to fastest. Each row is either critical or a broken signal you can act on today.
• Watch: smaller issues, or checks we couldn't score because there wasn't enough data. Worth keeping an eye on, but rarely urgent.
• Passed: checks your site cleared. A quick look now and then is a useful sanity check.

What each issue shows

• Title: a plain name for the problem.
• Why it matters: one sentence on why Google or your visitors care.
• Affected URLs: the pages where we found it, so you can go straight there.
• How to fix it: the change to make. Copy fix puts it on your clipboard.

Retest and change badges

Once you've shipped a fix, click Retest. The new audit is compared with the previous one, and a row can get one of two badges:

• Fixed: a rule that used to fail on that URL now passes.
• Regressed: a rule now fails on a URL where it passed before. New failures count as regressions too.

The comparison uses a frozen snapshot of your previous audit, so an older report keeps showing the same results.

llms.txt

/llms.txt is a newer convention: a plain-text file that points AI assistants (ChatGPT, Perplexity, Claude and others) to the pages you'd like them to read and cite. RankMeFast treats this rule as advisory. We suggest adding one, but nothing is broken without it.

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> is the headline people see in Google results. Give every page a specific title of 30–60 characters.
• Meta descriptions missing or duplicated: The short snippet Google shows below the title. Write a different one for each page.
• Page headings missing or overused: Use one <h1> per page, then <h2> and <h3> for structure. A missing <h1> matters a lot; two <h1>s matter less.
• Canonical link missing or broken: A <link rel="canonical"> tells Google which URL is the main version of a page. It causes problems when it is missing or points to another site.
• Structured data missing or broken: Machine-readable tags (JSON-LD) that help Google understand articles, products and 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 about 200 words look empty to Google. Expand the ones you want to rank.
• No FAQ signals found: We found no question-and-answer sections. FAQs help both visitors and AI assistants.
• llms.txt file missing (advisory): A newer convention: a /llms.txt file that points AI crawlers to your best content. It is optional, so this rule is advisory only.
• HTTPS not enforced: Your site should redirect http to https and use the https version as the canonical URL.
• Poor real-visitor performance: Real visitors had a slow experience on the page. The data comes from Google’s Chrome UX Report, and sites with little traffic may not have any yet.
• Low lab performance estimate: Our Lighthouse test run scored low. Scores vary by about 10 points between runs, so use this as a hint.
• Not mobile-friendly: The page doesn’t display well on phones. Check tap-target sizes and the viewport meta tag.
• Not indexed by Google: Google looked at the page but didn’t add it to search results. If this rule can’t get data, reconnect Google Search Console.
• Rich results issues: Google recognised your structured data but found errors that keep the page from showing enhanced results.
• Indexed with warnings: The page is indexed, but Google flagged a canonical or duplicate-content problem.

Back to the docs index