Free SEO Tools for Analyzing and Improving Websites

Free SEO tools can help you find what to fix, but no single tool answers every question. Start with Google Search Console for your site’s Google Search visibility and indexing, use a crawler such as Screaming Frog SEO Spider for page-level technical checks, add Ahrefs Free for verified-site audit and backlink context, and use PageSpeed Insights when you need to investigate page performance. Treat their data as complementary: Search Console reports Google’s view of your site, while third-party tools provide their own crawls and estimates.

This guide explains what each free option is for, its relevant limits, and a practical workflow for turning findings into fixes. It also shows how to capture a page for visual review when a rendering issue may be involved.

1. Choose a tool for the question you have

Question	Start here	What to keep in mind
Is my site appearing in Google Search, and are important pages indexed?	Google Search Console	It reports on Google Search presence; it is not a complete technical site crawl.
Are pages broken, missing metadata, duplicated, or connected through redirects?	Screaming Frog SEO Spider	The free version is limited to 500 URLs per crawl.
What audit and backlink context is available for a site I own?	Ahrefs Free	Verify the site; free Site Audit and report visibility have published limits.
Is a page’s performance worth investigating?	Google PageSpeed Insights	Use the current tool output and Google documentation to interpret specific measurements.

These answer different questions. A crawler finding does not tell you how Google Search reports impressions or clicks; Search Console does not replace crawling the site’s links and metadata. Third-party backlink or keyword data is also not the same as first-party Google Search Console data.

2. Establish a search and indexing baseline with Google Search Console

Google describes Search Console as a free service for monitoring, maintaining, and troubleshooting a site’s presence in Google Search. Use it to understand whether Google can find and crawl important pages, inspect indexing concerns, request re-indexing when appropriate, review search queries and clicks, and see issue alerts or linking-site information. Google also says a site does not need Search Console to appear in Search; it helps site owners understand and improve how Google sees their site. See Google’s About Search Console documentation.

Practical first checks

Add or select the property for the site you manage and complete its verification.
Inspect a few important URLs, such as the homepage, a key product or service page, and a recently published page. Check the reported indexing and crawl information for each.
Review the site’s search performance reports for queries, pages, clicks, and impressions available in the property. Use this as a baseline, not as a complete picture of all search engines or all technical issues.
Investigate reported indexing issues and alerts. Fix the underlying page or site issue before requesting re-indexing; a request is not a guarantee of indexing or ranking.
Return to the relevant report after changes to see whether the reported issue or search data changes.

Search Console is most useful when you can access and verify the property. Keep the distinction clear: it is Google’s reporting about your site’s appearance in Google Search, not an independent estimate of every search visit or a whole-site audit.

3. Crawl pages with Screaming Frog SEO Spider

Screaming Frog’s free SEO Spider can crawl up to 500 URLs per crawl. Its pricing page lists free-version functions such as finding broken links, errors, and redirects; reviewing titles and metadata, meta robots and directives; discovering exact duplicate pages; generating XML sitemaps; and creating site visualizations. Check the current feature comparison before relying on a particular advanced feature, since availability depends on the licence.

Run a bounded crawl

Download and open SEO Spider from Screaming Frog’s official page.
Enter the site’s starting URL and begin the crawl.
Review the results relevant to your goal: response errors and redirects, page titles and metadata, directives, duplicate pages, and internal links.
Export or record the affected URLs, then check a sample manually before making broad changes.
Compare the crawl scope with the site’s size. If it exceeds 500 URLs, treat this as a sample or partial crawl—not a complete audit. Focus on important templates and sections, or evaluate a crawler and licence that can cover the required scope.

A crawl reflects what the crawler could reach under its configuration and the site’s responses at that time. It cannot establish that every user or search engine sees the same rendered page. Dynamic sites, blocked paths, authentication, crawl settings, and server behavior can affect coverage; review the actual scope and verify consequential findings.

4. Add verified-site audit and backlink context with Ahrefs Free

Ahrefs calls its free account Ahrefs Free; Ahrefs Webmaster Tools is the previous name. For verified sites, its free offering includes Site Audit, Site Explorer, and Web Analytics. Ahrefs describes Site Audit as reporting technical and on-page issues, while Site Explorer provides keyword and page traffic context and linking-site information. Consult the current Ahrefs Free page for details and limits.

Ahrefs publishes a limit of 5,000 Site Audit crawl credits per verified project per month and up to 1,000 backlinks and 1,000 keywords visible at once. These are vendor-published limits and can change. Free verified-site data is useful for context about properties you control; do not treat estimates as equivalent to first-party Search Console reports or assume that free access provides unrestricted competitor research. Ahrefs says paid subscriptions have higher allowances and access to additional tools.

Use the data with its scope in mind

Create an account and verify a site you have permission to manage.
Run Site Audit within the project’s available crawl credits and inspect which URLs were included.
Use Site Explorer for additional keyword, page, and backlink context, keeping its visible report limits in mind.
Prioritize issues you can confirm and connect to a real page or site problem. Do not make a site-wide change solely because a third-party estimate differs from Search Console.

5. Investigate page performance with PageSpeed Insights

Google PageSpeed Insights is Google’s tool for analyzing a page’s performance. Enter the page URL and review the results it provides. The research available for this guide supports identifying the tool and its general purpose, but not detailed claims about metric definitions, thresholds, field-data availability, or a diagnosis procedure. Check the current tool output and Google’s linked documentation before interpreting a specific metric or prescribing a fix.

Analyze representative pages rather than assuming one URL represents every template. If performance is a concern, record the page and the reported result, investigate the relevant implementation, make one change at a time where practical, and run the analysis again. A score or single fix does not guarantee higher rankings.

6. Turn findings into an improvement plan

Use a repeatable loop so that free reports lead to specific work instead of a long, unprioritized issue list.

Choose a question. For example: “Is this key landing page indexed?” or “Which pages on this section return errors?”
Choose the matching source. Use Search Console for Google’s search presence, a crawler for reachable page structure, Ahrefs Free for verified-site audit and backlink context, or PageSpeed Insights for page performance.
Record the evidence and scope. Note the page or report, when you checked it, and any crawl, verification, or display limit that applies.
Confirm the issue. Check the affected page and relevant implementation. Distinguish a real defect from a tool’s estimate, a crawl limitation, or a report that covers a different data source.
Prioritize by impact and reach. Address confirmed failures on important pages first, then recurring issues across a template. Keep a short list of what changed and which report can show whether the issue changed.
Revisit the right report. Recheck the same URLs or Search Console report after changes. Search reporting and crawl updates may not be immediate, so do not interpret a single unchanged report as proof that a code change failed.

A compact working checklist

Important pages are identified and inspected in Search Console.
Crawl scope is known; no partial crawl is described as a whole-site audit.
Free account and report limits are recorded before drawing conclusions.
Third-party estimates are kept separate from first-party Search Console data.
Findings are confirmed before edits are made.
Each completed fix has a relevant follow-up check.

7. Capture a page when visual rendering needs review

SEO reports can identify a page or issue to investigate, but a screenshot is a useful supporting artifact when you need to see what a page looked like at capture time—for example, whether a key content area appears visually blank or a banner obscures it. A screenshot does not establish indexability, diagnose a ranking change, or replace the underlying page and report checks. The following Playwright example captures one page as a local PNG for review.

DIY: capture a page with Playwright

Install Node.js, create a project, and install Playwright. The first command installs the package; the second downloads its Chromium browser. Save the code as capture.mjs, replace the URL, and run node capture.mjs.

npm init -y
npm install playwright
npx playwright install chromium

import { chromium } from 'playwright';

const url = 'https://example.com';
const browser = await chromium.launch({ headless: true });
try {
  const page = await browser.newPage({ viewport: { width: 1440, height: 1000 } });
  const response = await page.goto(url, { waitUntil: 'networkidle', timeout: 60000 });
  if (!response) throw new Error('Navigation returned no main resource response');
  console.log(`HTTP ${response.status()} ${response.url()}`);
  await page.screenshot({ path: 'page.png', fullPage: true });
} finally {
  await browser.close();
}

networkidle can be unsuitable for pages with persistent network activity. If navigation times out, try waitUntil: 'domcontentloaded', then wait for a selector that identifies the content you need before capturing. A full-page capture can be large on long pages. Review the saved image alongside the page itself; local capture settings and browser rendering can affect what it shows.

Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server for developers. One GET request can return a screenshot or PDF; its capture options include full-page capture, element selection, device presets, custom waits, and other controls. See the ScreenshotNeo API documentation for the request options.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await Bun.write('shot.webp', res);

Replace the example target with the page you want to inspect. ScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before the shot; bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots, and 1,000 screenshots a month are free with no card; paid plans start at $5 for 3,000. The ScreenshotNeo website has product details. Sign up for 1,000 free screenshots a month with no card.

8. Troubleshooting common problems

Symptom	Likely cause	What to do
You cannot see a site’s Search Console data.	The property may not be verified, or the selected property may not match the site you intended to inspect.	Confirm access and verification for the correct property. Search Console data is tied to the property and its reporting scope.
A page is missing from a crawler report.	The crawl may not have reached it, may have stopped at the 500-URL free limit, or may be affected by the site’s crawl accessibility and tool configuration.	Check the crawl scope and starting point, inspect internal links and access, and describe a capped crawl as partial. Sample important sections or use a crawl that covers the needed scope.
A third-party count conflicts with Search Console.	The tools use different sources, indexes, estimates, and reporting scopes.	Compare like with like and use Search Console for Google’s reported search presence. Do not assume the numbers should match.
Ahrefs Free does not show the report or volume you expected.	The site may not be verified, or free crawl-credit and visible-result limits may apply.	Verify the property you manage and check the current free-account limits before interpreting the report.
PageSpeed Insights output is hard to interpret.	The exact metric or report context needs current documentation and page-specific interpretation.	Use the tool’s current explanation and linked Google documentation. Avoid inferring a cause from a score alone.
Playwright navigation times out.	The page may keep network connections active, require a longer load, or fail to load.	Inspect the response and page behavior; try `domcontentloaded` and wait for a specific content selector. Do not treat a screenshot as proof that the page is indexed.
The screenshot is empty or shows a challenge.	The page may have returned blank content, a bot check, or a load failure.	Check the HTTP response and page directly, and retry only after confirming access and load conditions. A capture cannot bypass a site’s access controls.

9. Performance, reliability, and cost

Stay within free limits. Screaming Frog’s free crawl is capped at 500 URLs. Ahrefs publishes 5,000 Site Audit crawl credits per verified project per month and visibility of up to 1,000 backlinks and keywords at once. Check current vendor pages because limits can change.
Reduce wasted work. Begin with important URLs and representative templates. A scoped crawl or small set of page checks can answer a defined question without implying full-site coverage.
Expect reports to differ. Search Console, third-party databases, crawlers, and page-performance tools observe different things. Record the source and scope with each finding.
Make changes traceable. Preserve the affected URLs and report details, change one class of issue at a time when practical, and revisit the report most relevant to that change.
Keep outcomes realistic. These tools expose information and possible problems; the cited sources do not promise rankings or traffic from a score or single correction.

Frequently asked questions

Do I need Search Console for Google to index my website?

No. Google says Search Console is not required for a site to appear in Google Search. It helps owners monitor and troubleshoot their search presence.

Can a free SEO tool analyze any website?

Some checks require access or verification. Search Console and Ahrefs’ free verified-site functions are intended for properties you can access or verify. A crawler can inspect reachable pages, subject to its crawl scope and the site’s behavior.

Is a 500-URL crawl enough for my site?

It is enough only if the pages and sections relevant to your question fit within the crawl. If your site is larger, label the result as a sample or partial crawl.

Will fixing every reported issue improve rankings?

No tool report guarantees a ranking change. Confirm that an issue is real, prioritize it based on the pages affected, and check the relevant report after the fix.

Sources and changing limits

Tool descriptions and limits above are based on the vendors’ published information: Google Search Console overview, Screaming Frog pricing and feature comparison, Ahrefs Free, and PageSpeed Insights. Product names, limits, and features can change; confirm current details before planning a recurring audit.