Quick Wins
How Quick Wins Are Chosen
Your reports pick fixes by severity and effort, never by a predicted score gain:
- Site dashboard. "What to do next" ranks the failing checks across your analyzed pages: worst severity first, then how much the check counts, then how many pages it fails on. Each fix is labelled with who usually does it and its effort (Quick, Medium effort or Larger project). The Quick wins number at the top of the dashboard counts the ranked fixes labelled Quick.
- Page report. In the Action Plan tab, Smart Recommendations (written when you ask for them, free within a daily limit) have a Quick Wins filter for the fixes rated at under an hour of work.
- Scan results. Each scan also keeps up to three quick wins, low-effort fixes for critical, high or medium problems, most severe first, plus PageSpeed suggestions that are usually quick, such as text compression or removing unused CSS. The MCP server returns them with the scan results.
Unproven checks are never among them: they are shown in the full report but not ranked.
5-Minute Fixes
Start here - these quick changes take little effort:
- Let AI search crawlers fetch your pages (robots.txt)
- Add a meta description
- Add a canonical URL that opens a live page
- Fix missing alt text
- Remove accidental noindex or nosnippet settings
- Add basic Schema.org that matches the page
- Add Open Graph tags
- Improve heading hierarchy
Let AI Search Crawlers Fetch Your Pages
Time: 2 minutes
AI search and assistants can only use pages their crawlers are allowed to open. Search crawlers (OAI-SearchBot, PerplexityBot, Claude-SearchBot, Bingbot, Googlebot) and user-fetch crawlers (ChatGPT-User, Perplexity-User, Claude-User) should not be blocked on pages you want found. Training crawlers (GPTBot, ClaudeBot, CCBot, Google-Extended and similar) are a separate choice: blocking them does not hide your pages from AI search. This example allows search and declines training:
# robots.txt - allow AI search, decline training (example policy) User-agent: OAI-SearchBot User-agent: Claude-SearchBot User-agent: PerplexityBot Allow: / Disallow: /admin/ User-agent: GPTBot User-agent: ClaudeBot User-agent: CCBot User-agent: Google-Extended Disallow: / User-agent: * Allow: / Disallow: /admin/
Optional: Add llms.txt
Time: 10 minutes
llms.txt is an optional summary file. Google does not use it and no major AI engine is shown to, so your report shows this check as unproven and does not score it. If you want one anyway, create a plain-text file at /llms.txt in the format llmstxt.org proposes:
# Your Company Name > One or two sentences on what your company or site does. ## Key pages - [Products](https://example.com/products/): what you sell - [About us](https://example.com/about/): who is behind the site - [Contact](https://example.com/contact/): how to reach you ## Optional - [Blog](https://example.com/blog/): articles and guides
Add Basic Schema.org Markup
Time: 15 minutes
Add this JSON-LD to your homepage's <head> section, and keep every value in it the same as what visitors see on the page (the Markup Matches Page check compares them). In sameAs, list only profiles that really are your company's:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "Organization",
"@id": "https://example.com/#organization",
"name": "Your Company Name",
"url": "https://example.com",
"logo": {
"@type": "ImageObject",
"url": "https://example.com/logo.png"
},
"description": "Brief description of your company",
"sameAs": [
"https://twitter.com/yourcompany",
"https://linkedin.com/company/yourcompany"
]
},
{
"@type": "WebSite",
"@id": "https://example.com/#website",
"url": "https://example.com",
"name": "Your Site Name",
"publisher": {"@id": "https://example.com/#organization"}
}
]
}
</script>
For Blog Posts / Articles
The headline, the author's name and the dates in the markup must also appear on the page.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Your Article Title",
"description": "Article description",
"author": {
"@type": "Person",
"name": "Author Name"
},
"datePublished": "2024-01-15",
"dateModified": "2024-01-20",
"publisher": {
"@type": "Organization",
"name": "Your Company",
"logo": {
"@type": "ImageObject",
"url": "https://example.com/logo.png"
}
}
}
</script>