1 page
Free- 836 SEO + AI rules
- SEO + AI readability
- Performance + accessibility
- PDF and repair priorities
SEO & AI AUDIT · FREE
Free SEO checker. Accelerate your organic growth.
Launch a website check for Google, ChatGPT and Claude in under a minute.
836 rules + SEO, AI readability, performance and accessibility measurements FREE.
Multi-page audit
$4.99- 836 rules on every page
- Choose the pages to audit
- One consolidated report
- Checks across the whole website
AI Audit
Coming soon$9.99- SEO-tailored copy
- GEO-tailored content
- .md skills for AI agents
- High-impact plan
Growth Audit
Coming soon$19.99- Full competitor analysis
- Your market position
- Realistic growth roadmap
- Strategic insights and priorities
Save $4.99 on any paid plan when you add our fukamo.audit badge to your website.
AUDIT OUR OWN WEBSITE
Try the report before checking your site.
Run the same checks on Fukamo. Open findings on the page preview, inspect their HTML evidence and download the repair plan.
Run this auditfukamo.com/sk
59/100Your website needs attention.
- Passed 241
- To review 17
- Failed 7
- Unavailable 8
- Critical 0
- High priority 5
- Standard priority 2
- To review 17
- 01Structured dataHigh priority×2
- 02SecurityHigh priority
- 03Performance signalsHigh priority
- 04PerformanceHigh priority
- Findings7 to fix241 checks passing
- Repair plan24 tasks7 fixes · 17 reviews
- Page data3,243 words10 images without alt
- Performance and accessibility66 / 100Mobile · Lighthouse
- Links and server282 links23 external links
Full reportSend by emailCopy linkShare linkBack to site
INSIDE YOUR REPORT
One audit. A clearer view of your website.
01 Findings and evidence
A checklist becomes useful when you can trace each finding to the page. Open the evidence and separate confirmed issues from checks that need your judgment.
- Filter by category and severity.
- Inspect the element and its HTML evidence.
- Keep manual review separate from confirmed failures.
02 Repair plan
Group related findings into practical repairs. Give your developer the context, affected pages and a plan they can work through.
- Start with the highest-priority repairs.
- See related findings and affected URLs together.
- Download the repair plan as a PDF.
03 Page data
Review the information your HTML actually contains. The page inventory puts metadata, headings and content in one place.
- Inspect the title, description and canonical URL.
- Review headings, images and alternative text.
- Check structured data and extracted page text.
04 Performance and accessibility
Google Lighthouse adds a measured view of loading, visual stability and accessibility. Switch devices to inspect the results and recommendations.
- Compare mobile and desktop lab results.
- Inspect LCP, layout shifts and blocking time.
- Open the accessibility and performance diagnostics.
05 Links and server
A page can look fine while its links or server responses need attention. Inspect the tested URLs alongside the network diagnostics.
- Review HTTP status codes and redirects.
- Inspect TLS and DNS information.
- Check compression and cache response headers.
Six views of what your page needs.
Understand what each score measures, then inspect the actual checks behind it.
Query match
Connect the audit to the phrase your customers use. Query analysis checks where the phrase appears and how the page addresses its intent.
- Search phrase — choose the primary query you want to evaluate.
- Matching evidence — review titles, headings, URLs and visible content.
- Coverage and intent — examine the match evidence instead of repeating keywords.
Overall HTML score
Start with the foundations in your page source. The HTML score brings scored checks together; the findings show which concrete changes deserve attention.
- Page structure — inspect headings, metadata and meaningful HTML.
- Weighted findings — confirmed failures affect the score according to their importance.
- Manual review — checks needing judgment stay separate from scored failures.
Google visibility
Check the page signals that help search engines access and understand your content. Follow each finding to its evidence before changing the page.
- Indexing signals — inspect robots directives and canonical URLs.
- Search presentation — review titles, descriptions and headings.
- HTML readiness — the score evaluates page checks, not your Google ranking.
AI visibility
See whether AI search crawlers can access the page and whether its HTML provides readable, structured information. Inspect the evidence behind the AI checks.
- Crawler access — review the rules for supported AI search bots.
- Readable content — inspect accessible text and semantic structure.
- Evidence and limits — readiness checks do not prove citations in AI answers.
Infrastructure
Give crawlers a consistent path through your site. This score focuses on the technical categories in the audit, with specific findings you can verify and repair.
- Indexing and canonical — inspect crawler instructions and preferred URLs.
- Links and languages — review navigation signals and language annotations.
- Security and HTTP — check the relevant page and response findings.
Visitor experience
A usable page needs to load well and work for more people. This score combines measured Lighthouse performance and accessibility for each available device.
- Performance and accessibility — both measurements contribute equally.
- Mobile and desktop — the lower available device score sets the summary.
- Measured diagnostics — open the lab metrics and concrete improvement suggestions.
YOUR FIRST AUDIT
Try an audit of our own website How to run your first SEO audit.
- 01
Choose a page and a phrase.
Use your service, product or article URL. Add the phrase you want this page to answer.
- 02
See the evidence.
Follow the scan or open the finished report. Start with confirmed issues, then review the checks that need your judgement.
- 03
Download the repair plan and verify your changes.
Download the findings, passed checks and repair plan as separate PDFs. Publish your changes and audit the same URL again.
SEO + AI, WITH EVIDENCE
Know what the audit proves.
Fukamo checks your page. Google decides what to index and rank. AI services decide which sources to cite.
Useful today
Locate technical barriers, compare your phrase with visible content, inspect crawler access and test the page experience. Each result points to evidence you can verify.
Measure after the repair
Use Google Search Console to check indexing, impressions and clicks. A higher audit score is a technical improvement, not a promise of traffic.
How to measure SEO results ↗SEO advice worth checking.
20 facts and common myths, with a practical next step and the original source. Open a topic that matters to your website.
10 myths to question
“Disallow removes a page from Google.”
Robots.txt controls crawling. Google can still list a blocked URL discovered through links, sometimes without a description. A blocked address and a removed search result are different outcomes.
Try this
For a public page you want excluded, use a crawlable noindex directive. Put private documents behind authentication.
“Disallow plus noindex is extra protection.”
Googlebot must fetch a page to read its noindex instruction. Blocking that same URL in robots.txt can hide the instruction you intended Google to follow.
Try this
Check a public thank-you page in URL Inspection. Confirm Google can retrieve it and sees noindex in the delivered HTML or header.
“Submitted in a sitemap means indexed.”
A sitemap helps Google discover pages. Submission does not promise a crawl or an indexed result, even when the file itself is processed successfully.
Try this
For a new service page, add a useful internal link and inspect the specific URL. A successful sitemap submission is only one piece of evidence.
“Google must show my meta description.”
Google primarily builds snippets from page content and may use your meta description when it describes the page better. The same URL can receive different snippets for different searches.
Try this
Put delivery terms on the product page itself; then write a specific description that accurately summarizes the offer.
“Every SEO page needs 2,000 words.”
Google says it has no preferred word count. A short opening-hours answer and a detailed migration guide solve different tasks; padding both to the same length adds no useful evidence.
Try this
List the reader’s unanswered questions. Add the missing explanation, worked example or limitation, and cut repeated introductions.
“Valid schema guarantees a rich result.”
Passing a structured data test establishes only part of eligibility. Google also considers content policies and the search context, and can choose a plain text result instead.
Try this
Compare your Product markup with the visible price and availability. Repair mismatches before adding more schema properties.
“Duplicate content automatically means a penalty.”
Ordinary duplicate URLs are not automatically a spam violation. They can still confuse visitors and waste crawling resources. Google usually chooses a representative URL.
Try this
Check whether tracking parameters create copies of a product page. Align canonical signals with the version you want customers to share.
“Adding meta keywords improves Google rankings.”
Google Search ignores the meta keywords tag. Filling it with search phrases does not help indexing or ranking.
Try this
Spend that time improving the visible title and answering the question behind your target phrase.
“Lighthouse 100 guarantees first place in Google.”
A perfect laboratory score is not a ranking guarantee. Google considers relevance and many other signals; good Core Web Vitals alone do not secure the top result.
Try this
Fix slow interactions that hurt customers, then check whether the page actually answers the search. Track field data alongside laboratory measurements.
“Every clickable button is a crawlable link.”
A button can navigate with JavaScript without exposing a link Google can reliably follow. Standard anchor elements with an href provide a discoverable destination.
Try this
Inspect a category card — does its HTML contain a real link to the category URL?
10 facts to work with
ChatGPT search and training have separate controls.
OpenAI documents OAI-SearchBot for search and GPTBot for potential model training. Their robots.txt settings are independent, so one blanket rule can make a broader decision than you intended.
Try this
If your policy permits search but excludes training, review separate groups for these two agents and verify the actual deployed file.
Claude also separates search from training crawls.
Anthropic distinguishes ClaudeBot, Claude-SearchBot and Claude-User. They serve model development, search and user-requested retrieval respectively; recognizing just one agent misses part of the access policy.
Try this
Write down which uses your site permits, then test the matching robots.txt groups. A rule for GPTBot says nothing about Claude-SearchBot.
Google’s AI features require no special AI text file.
Google says AI Overviews and AI Mode need no additional AI text file or special schema. Publishing llms.txt therefore does not establish eligibility or guarantee a citation in those features.
Try this
First check that the page is indexed, eligible for a snippet and clearly answers a relevant question in visible text.
Today’s Lighthouse run and CrUX cover different moments.
Lighthouse measures a simulated visit. PageSpeed Insights field data summarizes eligible real Chrome experiences over the previous 28 days, so yesterday’s speed fix will not instantly replace that history.
Try this
Compare mobile with mobile and check whether field data describes this URL or the whole origin before judging the change.
A repeated phrase can leave the real question unanswered.
Google’s spam policies flag unnatural keyword repetition intended to manipulate rankings. Counting mentions of “bicycle repair” cannot tell you whether the page explains services, turnaround or how to book.
Try this
Read the page as a customer with that query. Replace repetitive phrases with the missing decision-making information.
Canonical signals work best when they agree.
Google treats redirects and canonical annotations as strong canonical signals; sitemap inclusion is weaker. Pointing each signal at a different URL gives the crawler conflicting preferences.
Try this
After moving a service page, align the redirect destination, canonical, sitemap entry and internal links with the preferred replacement URL.
Lazy loading should not depend on a click from Googlebot.
Google Search does not interact with a page like a visitor. Content fetched only after clicking or scrolling can be missed; viewport-based loading should work without those actions.
Try this
Inspect rendered HTML in Search Console. For infinite lists, provide persistent pagination URLs with crawlable links.
HTTP 200 can still hide a soft 404.
A successful response code does not guarantee usable content or indexing. Google may treat an empty page or an error message served with HTTP 200 as a soft 404.
Try this
Test a nonexistent product URL. A real missing page should return the appropriate error status, not a successful empty template.
Alt text can describe the destination of an image link.
When an image acts as a link, Google uses its alt text as anchor text. A linked image without that description can lose useful context.
Try this
Check linked product photos. Describe the relevant product naturally instead of repeating a list of keywords.
The lang attribute does not translate a page for Google.
Google identifies a page’s language from its text, not the HTML lang annotation. Setting lang to English will not turn Slovak content into an English result.
Try this
Translate the actual content and navigation. Keep the correct lang attribute for accessibility and connect language versions with hreflang.
READ THE EVIDENCE
Good SEO starts with a useful page.
Make your answer worth finding.
Explain the actual offer, add your own examples and make claims verifiable. Useful contentgoes beyond repeating a keyword.
Google’s people-first content guidance ↗AI search still needs the basics.
For AI Overviews and AI Mode, Google points to established SEO practices. Check access, indexability and content people can understand.
How Google describes its AI search features ↗Measure the effect of a faster page.
Rakuten 24 used an A/B testto connect performance changes with shopping outcomes. Their study is a useful measurement example; your results depend on your site.
Read the Rakuten 24 experiment ↗Free SEO tools for your URL.
Choose what to check. Enter a URL and see the findings with source evidence.
Canonical URL Checker
Check canonical declarations and available target checks.
Schema Markup Checker (JSON-LD)
Check JSON-LD markup on a page for free. Inspect Schema.org types, syntax errors, missing properties and the source code.
Robots.txt Checker
Fetch the site’s robots.txt and evaluate crawler rules for the submitted page.
Meta Tag Checker
Check titles, descriptions and OG tags. Preview Google, Facebook and WhatsApp, then try better copy.
BEFORE YOU START
Questions about the free SEO audit.
The scope, the report and your next step.
Is the SEO audit really free?
Yes. The audit of a public page and its PDF reports are free, without an account or credit card. A wider domain crawl is a separate paid option shown in pricing.
Audit scope and pricing ↗What do I need to start?
A public page URL and the search phrase that matters most for that page. No installation, analytics access or administrator password is required.
Choose a useful search phrase ↗How long does the audit take?
The first findings appear as the scan progresses. Google Lighthouse runs in parallel and can finish later. Slow websites, provider queues and unavailable measurements can extend the wait.
Understand performance measurements ↗Does a good score mean I will rank in Google or ChatGPT?
No. The score describes the checks we could evaluate. It does not measure Google rankings, search volume or citations in AI answers. Use Search Console for actual search performance and examine real AI answers when evaluating citations.
Measure actual SEO results ↗Do you audit the whole website?
The free audit focuses on the URL you enter, with a sample of up to six internal pages. It is not an exhaustive domain crawl. Check your key page types separately or choose a wider crawl.
Choose pages for a technical audit ↗Will Fukamo change anything on my website?
No. Fukamo reads public content and reports findings. You decide which recommendations to apply. Check the context before changing page content, indexing rules or redirects.
What data the audit uses ↗What is included in the complete download?
A ZIP with three PDFs named Items to review, Passed and Repair plan. The files use the same check references so you can discuss a specific finding without copying the entire report.
What the PDF reports contain ↗Does AI write the audit?
The audit evaluates defined rules over fetched data; it does not ask a language model to score your website. AI readability describes technical access and content signals, not a prediction of AI recommendations.
How scoring works ↗Your next improvement is on your page.
Enter your URL to see the findings and download your repair plan.
Audit my page for free