DEV Community: Mustafa Aydemir

5 SEO Audit Tools for Websites in More Than One Language

Mustafa Aydemir — Sat, 14 Nov 2026 06:08:05 +0000

For a website in several languages, choose an SEO audit tool that can reach the related language versions, not just the homepage. Then separate two questions: are the pages technically usable, and are their language relationships configured correctly?

A healthy English page doesn't tell you whether its German equivalent redirects somewhere unexpected or points its canonical back to English.

These five tools help with different parts of that review. This is a comparison of official documentation checked on November 14, 2026, not a hands-on benchmark. I'm a co-founder of Screpy, which is included below.

Check the whole language group

Start with an inventory of equivalent pages. For example, these illustrative URLs represent one content group:

Language	URL	Evidence to record
English	`https://example.com/en/setup/`	Response, canonical and declared alternates
German	`https://example.com/de/einrichtung/`	Response, canonical and declared alternates
French	`https://example.com/fr/installation/`	Response, canonical and declared alternates

Google's localized-page guidance supports hreflang in HTML, HTTP headers or XML sitemaps. Those methods are equivalent from Google's perspective. Check the method your site actually uses.

The language versions should identify themselves and their alternates, with reciprocal links and fully qualified URLs. Don't assume a folder name proves the page contains the right language, or that an annotation proves Google has indexed it.

Tool	Useful role in a multilingual audit
Google Search Console	Inspect Google's indexed evidence for an individual locale URL
Screaming Frog	Investigate hreflang relationships with detailed crawl configuration
Sitebulb	Review international findings with guided reports
Ahrefs Site Audit	Review localization issues in a hosted audit workflow
Screpy	Investigate general technical findings across crawled locale pages

These roles overlap, but they aren't interchangeable. A status-code report and a reciprocal hreflang check establish different things.

1. Google Search Console

URL Inspection is the free starting point when the question is whether Google has indexed a particular language version. You need access to the property containing that URL.

Inspect representative pages from each locale rather than treating the default language as the entire website. Read the indexed result and Google-selected canonical. A live test answers a different question about current indexability; it doesn't predict Google's canonical choice.

For example, if the German setup page is missing from search, checking its indexed evidence is more useful than changing hreflang simply because a generic audit score dropped.

Search Console is useful evidence in the audit, but this URL-level workflow isn't a replacement for checking the complete set of alternate relationships. Keep the crawler's current observations separate from Google's stored version.

I'd use it alongside a crawler when an important translated page appears to be excluded or consolidated unexpectedly. Neither an accessible URL nor a successful live test guarantees indexing or rankings.

2. Screaming Frog SEO Spider

Screaming Frog's hreflang audit workflow covers annotations in HTML, HTTP headers and XML sitemaps. It is a useful option when you want to investigate the relationships in detail rather than just see an issue total.

The setup matters. Enable crawling and storing hreflang, and include linked XML sitemaps when they contain the annotations. For language versions on different domains, the tutorial explains the additional configuration needed to download and process those external pages fully. Checking an external URL's status alone isn't enough to inspect its return annotations.

The documented hreflang workflow requires a paid licence. The pricing page served during research showed €245 per user per year; it also offers other currencies. The free crawler's 500-URL limit doesn't mean that all advanced audit features are free. Practical paid crawl size still depends on memory and storage.

I'd compare it when your site spans several domains or when you need precise control over what the crawler follows. Record that configuration with the report so the next audit covers the same language group.

3. Sitebulb

Sitebulb's international auditing is worth comparing when your team wants organized hreflang findings and explanations. It checks alternate relationships and HTML language declarations alongside the wider technical audit.

Its International report guide makes an important coverage point: restricting the crawl to /de/ prevents it from validating incoming reciprocal annotations from excluded folders such as /en/ and /es/. Enable the International report and include XML sitemaps as a source if that is where your annotations live.

A reported mismatch is a reason to inspect the implementation. It isn't proof that the translation is wrong or that Google has selected the wrong language in search.

The Desktop plan comparison lists 10,000 URLs per audit for Lite and a default 500,000 for Pro. Pro adds capabilities such as audit comparisons and scheduling. Confirm that the selected tier includes the international analysis you need, rather than choosing solely by URL capacity.

The dynamic page returned no readable subscription amounts during research, so check the current price and billing period directly. I'd compare its guided workflow against the effort of configuring and interpreting a more manual crawl.

4. Ahrefs Site Audit

Ahrefs Site Audit offers a hosted workflow with localization checks alongside indexability, redirects, links and other technical findings.

One useful example is its documented multiple URLs for the same hreflang target issue. Two different URLs declared for the same en target are different from separate en-US and en-GB targets. Review the exact language-region code before merging or deleting annotations.

That distinction can help turn a generic localization warning into a specific template investigation. It doesn't establish whether the pages are useful equivalents or whether their translations preserve the intended meaning.

For verified websites, Ahrefs Free includes 5,000 crawl credits per project per month. Credits are consumed by HTML pages returning 200, rather than every redirect, broken URL or non-HTML resource. Check report access and crawl settings for your account before sizing the audit.

I'd compare it when you want ongoing hosted reports, especially if you already use Ahrefs. A monthly credit allowance isn't the same as an unlimited number of complete audits across every language.

5. Screpy

Screpy Website Audit fits the general technical side of a multilingual review: response codes, redirects, canonicals, metadata, headings and links across the pages reached by a crawl.

For a translated section, those findings can help identify a repeated problem such as missing titles, broken internal destinations or unexpected canonical targets. First check that the important locale URLs actually appear in the crawl inventory.

Coverage depends on links, depth, URL capacity and access. JavaScript rendering is available as a crawl setting, but it doesn't bypass authentication, bot protection or scope limits.

I wouldn't treat this general audit as proof that every reciprocal hreflang relationship is valid. For that specific job, compare the dedicated international workflows above. Likewise, an issue-free crawl doesn't establish translation quality.

The Pro plan lists five projects and 5,000 crawl pages per project, at a regular $192/year, equivalent to $16/month paid upfront. Count all relevant locale URLs against the selected crawl's capacity. Welcome discounts are conditional; check the final total and renewal terms. The seven-day trial becomes paid unless cancelled, and subscriptions renew automatically. AI Visibility is not included in Pro.

With Screpy MCP, an assistant can inspect supported completed-crawl findings and URL details while you investigate. Keep its answer tied to the selected crawl and affected URLs. Connecting the assistant doesn't grant more capacity or automatically repair your locale templates.

I'd compare Screpy when you want a practical technical fix queue alongside the rest of your SEO work, with a separate check for any language relationship the audit hasn't established.

Count locale URLs before choosing a plan

Suppose a site has 2,000 content pages, each published in three languages. That is 6,000 locale URLs before adding other crawlable pages. This is an illustrative sizing calculation, not a measurement of a real site.

A 5,000-page crawl limit could leave part of that inventory outside the audit. A monthly credit allowance may also need to cover repeat crawls after fixes. Check what the vendor counts and how separate domains or projects affect the allowance.

For the first review, choose one important content group and record the following for each language URL:

Is it in scope, reachable and serving the intended page?
What canonical and indexing directives does it declare?
Which alternates does it list, and do the other versions point back?
Does the content represent the same intended page for that audience?

Then expand the technical checks across the relevant templates. Keep a human language review in the process; structural validation can't tell you whether a translated instruction, product claim or call to action makes sense.

Choose the tool around the missing evidence. Use Search Console for Google's indexed view, a dedicated international crawler workflow for alternate relationships, and a broader audit workspace for technical patterns and follow-up work. The useful result is a complete enough inventory and a specific fix, not just a better-looking health score.

Which AI Bots Visit Your Website? A Look at 5 Tracking Tools

Mustafa Aydemir — Fri, 13 Nov 2026 06:05:52 +0000

To find out which AI bots visit your website, start with the requests reaching your CDN or server. A normal pageview dashboard can miss crawlers that fetch HTML without running its JavaScript.

Then ask what the record actually proves. A bot requesting a page, a human arriving from an AI app and your brand appearing in an AI answer are three different events.

These five tracking tools help with the request side. This is a comparison of official documentation checked on November 13, 2026, not a hands-on benchmark. I'm a co-founder of Screpy, which is included below.

Compare the collection layer first

Before comparing dashboards, check where the data comes from and which requests the integration can see. An origin-only feed and a CDN-edge view can cover different traffic. A cached response may never need to reach the origin.

Tool	Useful starting point	What to check before choosing it
Cloudflare AI Crawl Control	AI traffic at the Cloudflare edge	Zone coverage, available history and paid-only reporting
Known Agents	Dedicated agent analytics through a connector or backend integration	Event usage and the features included in your plan
Profound Agent Analytics	Server-log analysis inside a broader AI marketing platform	Supported log source and the quoted package
Scrunch	Agent traffic alongside AI visibility reporting	CDN/hosting integration and billing period
Screpy	Connected Cloudflare bot data alongside technical SEO	Zone scope, fixed reporting window and account availability

Also ask how the service identifies a bot. A familiar name in a user-agent string is weaker evidence than an identity check. Keep the product's actual classification attached to the finding rather than relabeling all automated traffic as verified AI activity.

These are workflow differences, not a ranking of which vendor detects every bot. None of the comparisons below establishes universal coverage.

1. Cloudflare AI Crawl Control

If your website's traffic already passes through Cloudflare, AI Crawl Control is a sensible first place to look. It is available on all Cloudflare plans and combines crawler reporting with access controls.

The analytics documentation describes request trends, crawler and operator breakdowns, status codes and popular paths. Filters include hostname and path, which matter when a zone contains several subdomains.

Read the counters carefully: all requests include blocked requests and error responses. Successful requests are those receiving a 200–299 response. A high request count therefore doesn't mean that the bot successfully received your articles that many times.

The core tool being available on every plan doesn't mean every report is free. Referral reporting is paid-plan functionality. Check the history and dimensions available to your account before planning recurring reports.

I'd start here before buying another subscription if the question is simply, “Which recognized AI crawlers are hitting our Cloudflare zone?” Its boundary is that collection layer; it doesn't describe traffic that never passes through it.

2. Known Agents

Known Agents, formerly Dark Visitors, is the more focused option here. Its Agent Analytics product breaks traffic down by agent, category and requested page, with failure analysis and spoof-verification features.

The setup guide separates website pageviews from API-call tracking and access controls. You connect the traffic you want to analyze through a supported integration or your backend; the dashboard can't describe a feed you haven't connected.

Its monthly pricing lists a free plan with one project and 100,000 events per month. Startup is $29/month, with three projects and one million events.

“Events” is the important word. Every API call counts, including identification requests and other API usage; individual items in a batch count separately. Don't size the plan as if the allowance represented unique human visitors.

I'd compare it when you want specialist bot reporting without starting with a broad AI visibility subscription. Check the feature matrix as well as the event allowance, particularly if exports, team access or reporting APIs are part of the requirement.

3. Profound Agent Analytics

Profound Agent Analytics uses server logs rather than JavaScript trackers for AI bot analysis. The product describes crawler verification and integrations with existing hosting and edge infrastructure.

That is worth comparing when a team wants incoming crawler activity alongside a broader AI-search workflow. The useful buying question is concrete: can your log source connect, and will the report preserve enough detail to investigate the pages and response outcomes you care about?

Keep its different evidence types separate. A platform can offer both crawler reporting and answer analysis without every recorded crawl proving a citation. Ask what source supports each metric instead of assuming that adjacent dashboard charts establish a causal connection.

The current pricing page lists a free trial and custom Enterprise packages. It doesn't provide a fixed Enterprise subscription amount to quote here. Confirm Agent Analytics scope, retention, export access and ongoing cost in the actual proposal.

I'd evaluate it as part of a wider team requirement, rather than assume the full platform is necessary just to count requests to a small documentation site.

4. Scrunch

Scrunch's bot-traffic documentation describes direct CDN and hosting integrations that collect requests and classify them by bot type and platform.

Supported connections include Akamai, AWS CloudFront, Cloudflare, Fastly, Vercel and WordPress. Check the integration route for your actual deployment before treating it as a plug-in replacement for whatever analytics you already use.

It is a candidate when you want agent traffic beside prompt and citation monitoring. Those are still different measurements: request activity can help explain access, while answer monitoring investigates what appears in the monitored responses.

The Starter plan is $300 month-to-month, or $250/month billed annually, equivalent to $3,000 for a year. The page lists agent traffic monitoring among the core capabilities, alongside limits such as 350 custom prompts and five page audits. The seven-day Starter trial requires no credit card.

I'd compare that bundle against the work you actually need. If bot reporting is the only requirement, include the narrower free or specialist options in the cost comparison instead of paying for prompt capacity you won't use.

5. Screpy

Screpy AI & Bot Traffic brings connected Cloudflare bot data into the SEO workspace. It needs a matching zone and an active token with the required access.

The view covers seven days of completed hourly intervals, excluding the incomplete current hour. It reports verified bot categories, request trends, transferred data and response outcomes. The scope is the Cloudflare zone, which can include other hostnames, rather than necessarily just the project's hostname.

You can inspect aggregated non-2xx paths for a selected crawler. “Unsuccessful” includes redirects as well as errors, so investigate the intended response before calling it a defect. Missing access or unavailable data isn't zero traffic.

This is analytics, not a raw request-log export or crawler-control tool. MCP exposes supported traffic-based Quick Wins, not the full bot-traffic dashboard, and doesn't fix the site automatically.

For budgeting, the general Pro subscription has a regular annual price of $192, equivalent to $16/month paid upfront, for five projects. The pricing page doesn't give AI & Bot Traffic a separate plan line or unlimited request allowance; confirm its availability in your account rather than infer it from that general price.

Welcome offers are conditional. Check your checkout total and renewal terms. The seven-day trial becomes paid unless cancelled, and subscriptions renew automatically. The separate AI Visibility feature is not included in Pro.

I'd compare Screpy when the next action is a technical SEO investigation and you want that request context alongside the rest of the project.

Turn a bot count into a useful investigation

Before subscribing, pick an important page and decide what finding would change your next action. Here are illustrative interpretations, not test results:

Observation	Useful next check
A crawler receives a 301 on an old article path	Confirm the redirect reaches the intended live destination
A crawler receives a 403	Check whether the access restriction is intentional before changing it
Repeated requests to an important route receive 5xx responses	Investigate that route and the response at the relevant collection layer
No requests appear	Verify the connection, hostname, time window and collection coverage before concluding no bots visited

Keep a short record: source, bot classification, hostname, path, response status, reporting window and intended behavior. That gives an engineer something actionable instead of “AI traffic looks bad.”

Start with the collection layer you already have. Cloudflare can answer the native edge question; Known Agents offers a focused agent workflow; Profound and Scrunch combine traffic with wider AI-search work; Screpy adds connected bot context to an SEO project.

Choose the one whose evidence and operating cost fit the question. You don't need another subscription just because a crawler has an AI name. You need a reliable enough record to decide whether anything needs fixing.

5 Core Web Vitals Tools: One-Off Checks or Ongoing Monitoring?

Mustafa Aydemir — Thu, 12 Nov 2026 06:06:04 +0000

Start with a one-off check when you need to investigate a slow page. Pay for ongoing monitoring when you need repeated evidence, a record of changes or someone to get notified when performance slips.

The important detail is what gets measured. A scheduled lab test, Google's historical field data and your own real-user monitoring answer different questions.

These five Core Web Vitals tools cover those different jobs. This is a documentation-based comparison, with sources checked on November 12, 2026, rather than a hands-on benchmark. I'm a co-founder of Screpy, which is included below.

Decide what evidence you need

Google's current Core Web Vitals are LCP for loading, INP for responsiveness and CLS for visual stability. The recommended good thresholds are 2.5 seconds, 200 milliseconds and 0.1 respectively, assessed at the 75th percentile and separated by device type.

Lab tests help reproduce a condition and investigate a change. Field measurements describe actual visits. Running a lab test every day doesn't turn it into field data.

Tool	Main job in this comparison	Important boundary
PageSpeed Insights	An on-demand lab check with available CrUX field context	Check whether field data covers the URL or the origin
Lighthouse	Local investigation and tests you automate yourself	You operate the recurring workflow
DebugBear	Managed synthetic tests, CrUX and real-user investigation	Choose the measurement coverage and subscription you need
SpeedCurve	Synthetic/RUM monitoring with performance budgets	Test volume and sampled traffic affect the quote
Screpy	Scheduled lab checks for selected URLs alongside SEO work	Current results, without a multi-point performance history or alerts in this view

A green lab score is useful diagnostic evidence. It doesn't certify that every visitor, page or interaction has a good experience.

1. PageSpeed Insights

PageSpeed Insights is a useful free starting point for a public URL. You get a fresh Lighthouse lab run and, where coverage exists, historical real-user information from the Chrome UX Report.

Read the two parts separately. The field data covers a trailing 28-day period, so a deployment today cannot instantly replace that entire window. Check whether the report describes the exact URL or the broader origin. If neither has enough samples, field data remains unavailable.

I'd use it to answer an initial question such as, “Is this article slow to display its main content, and does the available visitor evidence point in the same direction?” Then inspect the diagnostics rather than stopping at the overall score.

The standard web report is an on-demand check. If your real need is retained reports, automatic scheduling and notifications, plan that workflow separately. Repeated manual screenshots can document a baseline, but somebody still has to run and compare them.

2. Lighthouse

Lighthouse makes sense when you are already working on the page. It is open source and runs through Chrome DevTools, the command line or a Node module. DevTools also lets you audit pages that require authentication.

It shares the lab engine used by PageSpeed Insights, but gives you a different workflow: investigate a local change, inspect the report and repeat under comparable conditions before releasing it.

For example, you could compare the same landing page before and after changing its image delivery. Keep the page version and test conditions attached to each report. A single improved score doesn't establish a stable improvement across visitors.

You can build recurring checks around Lighthouse, including Lighthouse CI. The software is free; operating a reliable workflow still involves runner capacity, storage, configuration and someone responsible for failures.

Choose this route when your team wants control and can maintain it. Choose a hosted service when the value you need is less work managing tests, reports and notifications.

3. DebugBear

DebugBear combines scheduled synthetic tests, CrUX reporting and real-user monitoring. Its reports, comparisons and alerts are relevant when performance needs an ongoing owner rather than an occasional check.

The useful distinction is between detecting a lab regression and understanding a visitor's slow experience. Its real-user monitoring includes page-view details and investigation of slow interactions, including the elements and scripts associated with poor INP.

That can matter when the problem appears after someone opens a menu or uses a filter, rather than during the initial page load. A loading diagnostic alone may miss the interaction you care about.

Before subscribing, decide whether you need synthetic testing, RUM or both. Ask for a quote against your actual URLs, test cadence and traffic coverage, rather than assuming a headline price covers the whole setup.

The current pricing page returned a JavaScript-only shell during this research, so I couldn't verify a subscription amount. I wouldn't use an older comparison's price to make that decision.

4. SpeedCurve

SpeedCurve is another option for a team combining synthetic testing and real-user monitoring. Its performance-budget workflow is especially relevant if you want a threshold crossing to reach someone who can investigate it.

The budget and alert features support absolute limits and rate-of-change thresholds, with notifications through email or webhooks. The deploy API connects release activity with performance investigations.

For a frequently updated product, that gives the team a clearer handoff: review the affected metric, compare the release context and decide whether the change needs investigation. An alert establishes that a threshold was crossed; it doesn't prove which code change caused it.

The pricing page lists plans starting at $90 USD per month, with the quote sized around RUM page views and synthetic checks. It also displays a 20% annual-billing saving. Check the selected billing period and included volumes before treating the starting figure as your budget.

I'd compare it when retained monitoring and release ownership are part of the requirement, rather than paying for that workflow just to investigate one slow page.

5. Screpy

Screpy Core Web Vitals fits a different job: keeping selected public URLs under scheduled lab checks while you work on technical SEO in the same workspace.

The URL table reports FCP, LCP, CLS, TTFB and TBT. Active eligible pages become due for another check after one day, subject to availability and plan access. That isn't a guarantee of a result at the same clock time every day.

There is an important boundary: TBT is not INP, and this feature doesn't report INP. Its lab PASS badge also doesn't certify Google's field-based Core Web Vitals assessment. Missing measurements need attention even when the available subset looks good.

The PageSpeed workflow shows current results, without a multi-point performance history or performance alerts in that view. Save your baseline if you want a meaningful comparison after a change. If automatic regression notifications and historical reports are essential, compare the dedicated monitoring services above.

The Pro plan includes five projects and 25 Core Web Vitals URLs per project. Its regular annual price is $192, equivalent to $16/month paid upfront. Welcome discounts are conditional; check your offer and checkout total. The seven-day trial becomes paid unless cancelled, and subscriptions renew automatically. AI Visibility is not included in Pro.

You can also use Screpy MCP to ask an assistant about the saved homepage lab overview. That tool reads available measurements with their URL and check time; it doesn't run a new performance test, return every monitored URL or fix the website. Access and plan eligibility still apply.

Size the monitoring job before subscribing

Before comparing prices, write down the pages, conditions and frequency you actually need. Google's Core Web Vitals workflow guide is a useful reference for combining diagnosis with field evidence instead of expecting one report to answer everything.

Here's an illustrative sizing calculation, not a recommended schedule or a measured result:

6 URLs × 2 test profiles × 2 runs per day × 30 days = 720 scheduled checks.

If you repeat each combination three times, that becomes 2,160 runs. Vendors may count checks differently, so map that workload to their billing definition. For RUM, also decide what traffic to collect or sample. A URL allowance and a monthly run allowance aren't interchangeable.

Keep a small baseline record with the URL, device/profile, measurement source, timestamp and release version. When a result changes, first check that you're comparing the same conditions. Then investigate the page; don't assign the cause from the score alone.

For an isolated investigation, start with PageSpeed Insights or Lighthouse. For a maintained regression workflow, compare DebugBear and SpeedCurve against your coverage and alerting needs. For scheduled current lab checks alongside SEO work, compare Screpy with its limits in mind.

The useful purchase is the one that helps someone take the next action. More reports won't help much if nobody owns that action.

Missing From Google? 5 Tools to Diagnose Indexing Problems

Mustafa Aydemir — Wed, 11 Nov 2026 06:15:04 +0000

If an important page is missing from Google, start by checking its index state in Search Console. Buying another crawler won't tell you, by itself, whether Google has indexed that exact URL.

A crawler becomes useful when you need to investigate the technical conditions behind the problem: a template adding noindex, a conflicting canonical, an inaccessible page or a weak discovery path.

These five tools help with different parts of that investigation. This comparison uses official documentation checked on November 11, 2026, not hands-on test results. I'm a co-founder of Screpy, which is included below.

Separate index status from indexability

Keep three questions separate: what Google last recorded, what the page serves now, and what your crawler observed. Those answers can disagree without any tool being broken.

A successful HTTP response and an apparently indexable page aren't proof of inclusion in Google's index. Likewise, an indexed URL isn't guaranteed to appear for the query you tried.

Tool	Useful diagnostic evidence	What to keep separate
Google Search Console	Google's indexed-page information and a separate live test	Live eligibility isn't an indexing promise
Screaming Frog	Technical crawl data, optionally joined with authenticated URL Inspection data	A normal crawl alone doesn't establish Google index status
Sitebulb	Guided investigation of directives, canonicals and technical patterns	Indexability hints aren't Google's index database
Ahrefs Site Audit	Hosted crawl reports for technical investigation	An audit score doesn't establish index inclusion
Screpy	Google inspection results alongside crawl context for eligible URLs	Completed inspected rows aren't the entire website inventory

Google's crawling and indexing troubleshooting guide is a useful reference when narrowing the issue. First decide whether this is a URL that should be indexed. Duplicate alternatives and intentionally excluded pages may be behaving correctly.

That decision comes before treating every “not indexed” label as a bug.

1. Google Search Console

For a specific URL on a property you can access, URL Inspection is the starting point. Read the indexed result, its crawl information and the Google-selected canonical before changing the page.

Then use the live test when you need to investigate current access or indexability. It answers a different question from the stored indexed result and cannot predict which URL Google will select as canonical.

For patterns across the site, use the Page indexing report. Group affected pages by reason and compare their purpose. A duplicated URL with a correct canonical needs a different response from an important original article that hasn't been indexed.

The report's example lists are limited to 1,000 URLs and aren't guaranteed to contain every URL in a status. Use URL Inspection for an individual page rather than assuming absence from an example list is the answer.

Search Console is free, but requires the relevant property access. I'd exhaust this evidence before paying for another tool simply to check a handful of URLs.

2. Screaming Frog SEO Spider

Screaming Frog fits when you need to line up URL-level technical evidence across many pages and investigate repeated conditions.

Its URL Inspection API workflow brings Google's indexed-page information into the crawl alongside technical data. That lets you distinguish a page the crawler considers indexable from a page Google reports as indexed.

The connection requires the appropriate Google account and property access, and inspection quotas still apply. It isn't a way to submit URLs for indexing.

The free edition crawls up to 500 URLs, while API integrations, JavaScript rendering, saving crawls and crawl comparison require a paid licence. The live pricing page served during research showed €245 per user per year. Hardware still limits practical crawl size.

I'd compare it when a missing-page problem appears to follow a route pattern or template. Check the affected URLs, their directives and their inspection records together, rather than interpreting the crawler's indexability column as Google's final decision.

3. Sitebulb

Sitebulb is worth considering when the next step is understanding and explaining a technical pattern.

Its Indexability Hints cover robots directives, X-Robots-Tag headers, canonicals and conflicts between signals. Examples include mismatched directives in HTML and headers, or a canonical that points to a URL with an error response.

For a developer, that can turn “these pages aren't indexed” into a narrower hypothesis: several URLs may share the same incorrect template output. Inspect representative pages before applying one change to the entire group.

The Desktop comparison lists 10,000 URLs per audit for Lite and a default 500,000 for Pro. JavaScript crawling is included in both; native audit comparisons and scheduling are Pro features.

Exact subscription amounts weren't available in the dynamic pricing page returned during research, so check the current quote and billing period rather than relying on an older price.

Treat the hints as technical evidence. They can help explain barriers, but they don't independently establish whether Google has indexed a URL.

4. Ahrefs Site Audit

Ahrefs Site Audit offers hosted technical investigation across areas such as indexability, redirects, robots and sitemaps. Its URL details and page exploration tools help you inspect crawl findings rather than stop at an overall health score.

Use that evidence to test a hypothesis. For example, compare the directives and content returned for an affected article with a similar working page. A successful response alone doesn't establish that the right content or canonical was served.

For websites you can verify, Ahrefs Free includes Site Audit with 5,000 crawl credits per project per month. Credits count HTML pages returning 200; redirects, broken URLs and non-HTML resources don't consume that allowance.

That is a monthly allowance, not a promise of unlimited repeat audits. Check coverage and report eligibility for your account before planning a large investigation.

I'd compare it when you want hosted crawl reports as part of an existing SEO workflow. Keep the Google index-state check in Search Console; a third-party technical audit isn't a replacement for it.

5. Screpy

Screpy Index Status combines Google inspection results with crawl context such as internal links, depth and heading counts. That is useful when you need to group affected URLs and decide which pages deserve a closer investigation.

The documented prerequisites are a matching connected Search Console property and a completed website crawl. The audit covers eligible URLs from that crawl, not every address that may exist on the site.

Coverage matters here. The feature selects successful 2XX URLs with no canonical or a matching canonical. Its result table contains completed inspections; skipped or failed requests aren't evidence that a URL is indexed or unindexed. Exports cover the current table page, up to 50 rows.

The general Pro plan lists five projects, 5,000 crawl pages per project and Search Console access at a regular $192/year, equivalent to $16/month paid upfront. Confirm Index Status availability and inspection capacity in your account; the pricing page doesn't publish a separate unlimited inspection allowance. Welcome offers are conditional, subscriptions renew automatically, and the seven-day trial becomes paid unless cancelled in time.

Stored inspection information may be reused, so a new audit doesn't guarantee an immediate view of a recent fix. MCP can inspect existing Index Status audits and records; it doesn't start a new audit or automatically repair the site.

Keep a diagnosis record before changing the page

Start with a few important URLs that should appear in search. Record the intended canonical, Google's reported state, the observation date and the current technical evidence.

Here's an illustrative diagnostic table, not a set of test results:

Evidence	What it establishes	Useful next check
The crawler reports `noindex` on an article that should be searchable	The crawler saw an exclusion directive	Inspect current HTML and response headers, then trace the template or setting responsible
A URL is technically accessible, but Google reports “Crawled - currently not indexed”	Technical access hasn't established index inclusion	Review the intended canonical, duplication, page content and discovery context before choosing a change
An alternate URL is excluded while the intended canonical is indexed	The alternate may be correctly excluded	Confirm that the canonical matches the purpose of the pages before treating the exclusion as a defect

Keep the source of each finding attached to it. “Crawler, this morning” and “Google inspection, last processed version” aren't interchangeable observations.

After a repair, verify the live condition first. Then allow Google time to process the change and review the indexed evidence separately. Repeating an audit against cached inspection information doesn't establish that a fix failed.

If the page is already indexed but doesn't appear for the query you want, investigate relevance and search performance rather than repeatedly changing indexing directives.

For a handful of pages, Search Console may be all you need. Add a crawler or an inspection workspace when the problem spans templates, URL groups or a recurring handoff. Choose the tool that helps you explain the evidence and the next action, not one that promises to put every URL into Google.

5 Internal Link Audit Tools for Blogs With Hundreds of Posts

Mustafa Aydemir — Tue, 10 Nov 2026 06:04:10 +0000

Once a blog has hundreds of posts, remembering what should link to what stops being a realistic workflow. New articles get attention. Older guides can become difficult to reach, even when they're still useful.

An internal link audit should help you find the next edit: a missing path, a broken destination, an unclear anchor, or a shared template sending readers to the wrong place. Adding more links isn't always the answer.

Here are five tools to compare for that job. This is a documentation-based comparison checked on November 10, 2026, not a hands-on benchmark. I'm a co-founder of Screpy, which is included below.

Count useful paths, not just links

Start with an inventory of the posts you want readers to find. A CMS export or sitemap can give you URLs to compare against the pages reached by a crawl. A page missing from a crawl isn't automatically orphaned: access rules, rendering and crawl limits may explain the gap.

Then separate total link occurrences from unique source pages. A link repeated in several places on one post doesn't create several independent paths from different articles. Also inspect where links appear. A sitewide footer and a relevant paragraph do different jobs for a reader.

Tool	Useful audit job	Main boundary
Screaming Frog	Sort incoming links and inspect their sources	Desktop workflow; free crawl stops at 500 URLs
Sitebulb	Review depth, anchors and link distribution with guided reports	Audit comparison and scheduling require Desktop Pro
Ahrefs Site Audit	Investigate link relationships in a hosted audit	Free entry access requires verified sites and has monthly crawl credits
Link Whisper	Review WordPress post relationships and act inside the CMS	Free reporting and Premium editing features differ
Screpy	Trace recorded destinations back to source pages and repeated uses	Crawl coverage and current-page export limits matter

Google's link best practices recommend contextual links and descriptive anchors. They don't prescribe a magic number of links per page.

Choose the tool around the question you need answered, not the highest link count in its dashboard.

1. Screaming Frog SEO Spider

Screaming Frog fits when you want detailed crawl data and are comfortable turning it into an editing list yourself.

Its internal linking audit guide explains how to sort the Link tab by Unique Inlinks. Three links from one source page count as three total inlinks but only one unique inlink. That distinction helps you investigate an important guide whose incoming links are concentrated on very few pages.

Inspect the actual sources before changing anything. A low count can identify a candidate for review; it doesn't prove the article needs links from unrelated posts.

The free edition and paid licence have different boundaries. Free crawling covers up to 500 URLs. JavaScript rendering, saved crawls, custom search and crawl comparison are paid features. The live pricing page showed €245 per user per year during research; crawl scale still depends on memory and storage.

A blog with 400 posts may exceed the free allowance once other discovered URLs enter the crawl. Check coverage before treating the report as your whole archive.

2. Sitebulb

Sitebulb is worth comparing when you want to explain the structure of a large archive, rather than only export errors.

Its internal linking documentation covers incoming followed links, crawl depth and anchor analysis. In Link Explorer, you can inspect incoming relationships for a target URL or review links using particular anchor text.

For orphan candidates, the documented workflow compares crawl discovery with additional sources such as XML sitemaps, analytics, Search Console or URL lists. Those extra sources matter: a crawler following links cannot discover every page that has none.

The Desktop plans list 10,000 URLs per audit for Lite and a default 500,000 for Pro. Both list JavaScript crawling; native audit comparisons and scheduling are Pro features.

Exact prices were unavailable in the dynamic pricing page returned during this review. Check the current currency, billing period and user count before purchasing.

I'd shortlist it when depth and source relationships need to be understood by someone beyond the person running the crawl. Keep its metrics as diagnostic clues, not Google's ranking scores.

3. Ahrefs Site Audit

Ahrefs Site Audit provides a hosted option for investigating internal link relationships. Its documented tools include Link Explorer, URL details with inlinks and outlinks, and bulk issue exports.

That makes it a candidate when you want source and destination evidence alongside a broader technical audit, without making a desktop application the centre of the workflow.

For a website you can verify, Ahrefs Free includes Site Audit with 5,000 crawl credits per project per month. Ahrefs says these credits count HTML pages returning 200; redirects, broken URLs and non-HTML resources don't consume that allowance.

Plan around repeated audits, not just one archive scan. Two complete crawls of a 3,000-page HTML archive would need more than 5,000 such credits. That's an illustrative calculation, not a measured crawl result.

Start with the free verified-site access and check the reports you actually need. A general product feature list shouldn't be read as a promise that every report, allowance or advanced workflow is included at every access level.

4. Link Whisper

Link Whisper is the WordPress-specific option here. Its appeal is the shorter distance between finding an underlinked post and editing links inside the CMS.

The publisher's free plugin description lists incoming link counts, outgoing internal and external link counts, and suggestions you can copy into your content. It distinguishes these from Premium features such as bulk insertion, auto-linking and full broken-link reporting.

An accessible official Starter offer listed $97/year for one site, with 2,000 AI credits included. That is an annual charge, not an $8 monthly subscription. Confirm current checkout terms and how the included credits apply to your planned work.

I'd compare it when your blog runs on WordPress and the bottleneck is making relevant editorial changes across old posts. For another CMS, a platform-independent crawler is a more natural starting point.

Review each proposed source, anchor and destination before accepting bulk changes. A suggestion can help you find a connection; it doesn't establish that the link improves the paragraph for a reader.

5. Screpy

Screpy fits the maintenance side of an internal link audit: investigate recorded destinations, trace source pages and decide whether an issue belongs to an individual post or a shared template.

Its link investigation workflow groups destinations from a completed crawl and separates usage counts from source-page counts. You can search by destination, source URL, anchor text or relationship attribute, then inspect the actual page before editing.

Keep the output boundary in mind. Table exports cover loaded destination rows on the current page, while Source Pages opens separately without an export control. This isn't a complete exported link graph or proof that every orphaned post has been found.

The Pro plan includes five projects and 5,000 crawl pages per project. Its regular annual price is $192, equivalent to $16/month paid upfront for the year. Conditional welcome offers can change the checkout total. Subscriptions renew automatically; the seven-day trial becomes paid unless cancelled in time.

I'd compare Screpy when link repairs sit alongside ongoing website audits. MCP can help an assistant investigate supported crawl evidence, but it doesn't automatically edit your posts. Recrawl after repairs and keep the coverage comparable.

Turn the audit into a short editing queue

Don't start by accepting every suggestion. Pick a small set of important posts and record the evidence for each proposed change.

For an illustrative 600-post blog, the queue might look like this:

Finding	Check before editing	Useful next action
An evergreen guide appears in the CMS inventory but not in the discovered link map	Was the guide excluded, blocked or beyond the crawl limit?	If it is genuinely isolated, link from a relevant existing guide or topic hub
A tutorial receives many link occurrences from very few source pages	Are these repeated template links rather than editorial references?	Review related articles for a helpful contextual connection
A removed article is still linked from several posts	Which destination now answers the reader's question?	Update the source links to the relevant current page
An anchor says “click here”	Does the destination deserve a link in this sentence?	If so, describe the resource clearly in the surrounding text and anchor

Keep the source URL, target URL, reason, owner and verification date. That is more useful to an editor than a list of pages sorted by a mysterious score.

After publishing changes, check representative source pages and rerun the relevant audit with comparable settings. Confirm the intended links exist and lead to the right content. Fewer reported issues can also mean fewer pages were reached.

For a WordPress archive, Link Whisper can bring reports closer to editing. For detailed crawl analysis, compare Screaming Frog and Sitebulb. Ahrefs offers a hosted audit starting point, while Screpy brings source investigation into ongoing technical maintenance.

Use the option that helps you make and verify the next useful edit. A larger link count isn't the outcome you're trying to ship.

5 Broken Link Checkers for Your Next Website Migration

Mustafa Aydemir — Mon, 09 Nov 2026 06:04:38 +0000

A migration can leave you with a clean homepage and a collection of broken paths underneath it. The useful broken link checker is the one that helps you find those paths, locate the links that send people there, and verify the replacement.

These five tools cover different parts of that job. Start with the access and crawl coverage you need before buying a larger plan.

This is a comparison based on official documentation checked on November 9, 2026, not a hands-on benchmark. I'm a co-founder of Screpy, which is one of the tools below.

Check old routes and new links separately

A crawl of the new site answers: which links can the crawler discover now? Your old URL list answers a different question: what happens when someone opens an address that existed before the move?

If an old route disappears from navigation, crawling the new homepage may never reach it. Keep a separate mapping of old URLs to their intended replacements. Google's site-move guidance covers building that inventory and updating internal links.

Tool	Useful migration job	Access or capacity to check
Screaming Frog	Inspect source links and explicitly check an old URL list	Free: 500 crawled URLs; advanced features require a licence
Sitebulb	Investigate broken URLs, redirects and audit changes	Desktop Lite: 10,000 URLs per audit; audit comparisons require Pro
Dr. Link Check	Run a focused hosted link check	Free Lite: 1,500 unique links per website, two projects, one-time checks
Ahrefs Site Audit	Audit a verified site without running a desktop crawler	Ahrefs Free: 5,000 crawl credits per project per month
Screpy	Trace failed destinations to source pages alongside technical audits	Pro: five projects, 5,000 crawl pages per project

Those limits use different units. A page can contain many links; a monthly credit allowance isn't a per-crawl page limit.

Before comparing reports, check whether the crawler can reach staging, pass any required authentication and see links created by JavaScript. A partial inventory can still be useful, provided you know what's missing.

1. Screaming Frog SEO Spider

Screaming Frog is the option I'd look at first when the migration involves a spreadsheet of old routes and someone needs source-level evidence for repairs.

Its broken-link tutorial shows the workflow: filter Response Codes to Client Error (4XX), select a failed URL, then inspect Inlinks to find the pages pointing to it. The bulk 4XX Inlinks export includes sources and destinations.

For the old route inventory, use List mode to supply URLs explicitly rather than relying on discovery from the new homepage. Inspect redirect outcomes separately; the immediate source of a failure can itself be a redirect.

The free edition covers up to 500 URLs. JavaScript rendering, saving crawls, scheduling and crawl comparison are paid features. The pricing page served during research showed €245 per user for one year. Paid crawl capacity still depends on memory and storage.

The tradeoff is hands-on work. You get detailed data, but you still need to decide whether a final destination is the right replacement.

2. Sitebulb

Sitebulb is worth comparing when you need to explain why a migration finding matters, rather than hand over a raw error export.

Its documentation separates broken internal URLs from redirect problems, including redirects that end in a 4XX or 5XX response and loops. That distinction helps when an old URL appears to redirect successfully at first, but the chain never reaches a usable page.

Choose the plan around the investigation. The Desktop plan comparison lists 10,000 URLs per audit for Lite and a default 500,000 for Pro. JavaScript crawling is listed for both; native audit comparisons and scheduled audits are Pro features.

The exact subscription amounts didn't load in the pricing page available during this review, so I'm not quoting an old price. Check the current currency, billing period and user count before buying.

I'd evaluate Pro when before-and-after audit comparison is part of the migration handoff. Don't buy Lite expecting that particular workflow just because its crawl limit fits the site.

3. Dr. Link Check

Dr. Link Check suits a narrower job: crawl a website's HTML and CSS, check discovered internal and external destinations, and find the locations that need an edit. It also checks referenced resources such as images and style sheets.

The important buying detail is its definition of a link. The pricing page counts each unique document or resource once, even when several pages reference it.

Lite is free for two projects and 1,500 links per website, with one-time checks. Standard is $13/month for five projects and 10,000 links per website, with monthly or biweekly scheduled checks. Weekly and daily schedules belong to higher tiers.

That can be useful for checking a small public site after launch without buying a full SEO suite. But don't read “1,500 links” as “1,500 pages,” and don't assume the entry paid plan runs daily.

For a migration, keep the old URL mapping as a separate acceptance checklist. A discovery crawl can check what it finds; it doesn't establish that every retired route has been tested.

4. Ahrefs Site Audit

For a site you can verify, check Ahrefs Free before assuming you need a paid Ahrefs subscription. It includes Site Audit and a documented allowance of 5,000 crawl credits per verified project per month.

The counting rule matters. Ahrefs says those credits are used for HTML pages returning 200; broken URLs, redirects and non-HTML resources don't consume that allowance. It isn't the same as a 5,000-URL limit on one migration crawl.

This is an option when you want hosted technical audit reports for a site you control. Confirm verification and crawl access before relying on it for staging.

Also separate Site Audit from the public Ahrefs Broken Link Checker. The public tool can surface broken inbound and outbound link records, but a quick lookup isn't proof that a fresh audit has checked your complete migration inventory.

I'd start with the free verified-site access, inspect whether it covers the routes you need, and only consider paid access when a specific limit or missing workflow justifies it.

5. Screpy

Screpy's Broken Link Checker works from a completed crawl. It groups destinations and lets you inspect source pages, which helps separate one missing route from a shared navigation link repeated across the site.

For migration cleanup, review broken destinations and the separate 3XX view. The grouped table isn't a full redirect-chain viewer. Check the final destination directly.

There's also an export boundary worth knowing: CSV and Excel exports cover loaded destination rows on the current table page. Source Pages opens separately and has no export control. Don't treat that export as a complete source-by-source migration checklist.

The Pro plan includes five projects and 5,000 crawl pages per project. Its regular annual price is $192, equivalent to $16/month paid upfront for the year. Welcome pricing is conditional; I'm using the regular price here. Subscriptions renew automatically, and the seven-day trial becomes paid unless cancelled in time.

I'd compare Screpy when link cleanup belongs alongside your ongoing technical audits. MCP can help an assistant investigate supported crawl findings, but it doesn't automatically repair your website. After edits, run a new crawl with comparable coverage.

Verify the migration, not just the error count

Whichever broken link checker you choose, keep a small record that someone else can verify. For each important route, record the old URL, expected destination, observed response and final URL. For links on the new site, also keep the source page and anchor.

Here's an illustrative acceptance table, not a test result:

Case	What you observe	Decision
`/docs/install` should move to `/help/install`	Old route redirects to the intended installation guide, which returns 200	Mapping works; update controlled source links to the new URL
`/guides/setup` still links to `/docs/install`	The old route returns 404	Repair the source link and the missing migration redirect
An intentionally retired page has no relevant replacement	It returns 404 or 410, and no current navigation points there	Don't invent an unrelated redirect just to reduce the error count
Every old guide redirects to the homepage	The final response is 200	Still investigate: a successful response doesn't make the destination relevant

Google specifically warns against sending many old URLs to an irrelevant homepage. A green status code alone isn't the acceptance test.

After repairs, repeat the old-URL checks and the new-site crawl. Keep the starting scope, page capacity and rendering settings comparable. Otherwise, a lower error count might simply mean the second crawl reached fewer source pages.

For a small migration, a free checker may be enough. Pay when you need the coverage, repeatability, source exports or audit comparison that your actual workflow requires. The useful result is a working path to the right content, with evidence you can hand to the next person.

New Website? Compare 5 Backlink Checkers Before You Subscribe

Mustafa Aydemir — Sun, 08 Nov 2026 06:04:40 +0000

If you've just launched a website, you may not need a paid backlink checker yet. Checking who links to your own site is a different job from researching competitors, exporting large reports or tracking changes over time.

Start with the question you need answered. Then pay for the access that answers it.

Here are five options to compare, including free starting points and paid plans. This is a documentation-based comparison using official sources checked on November 8, 2026, not a benchmark of which database finds the most links.

Disclosure: I'm a co-founder of Screpy, which is included below.

Decide what you need to check

Before comparing prices, separate three questions: who links to your website, where competitors get links, and whether a particular recorded link still exists.

Tool	Useful starting point	Main limit to understand
Google Search Console	Free Links report for a property you can access	A sample, not an arbitrary competitor lookup or complete live inventory
Ahrefs	Ahrefs Free for verified sites; a separate public checker for other targets	Verified-site access and public previews have different limits
Majestic	Lite for dedicated backlink research	Fresh Index and per-search allowances; Historic Index requires Pro
SE Ranking	Public checker before evaluating the wider paid suite	Public checks, trial access and paid exports aren't equivalent
Screpy	Max for backlink analysis alongside website audits and monitoring	Pro excludes backlinks; scope is the project or an added competitor domain

A backlink is a link record; a referring domain is a website supplying links. Ten links from one domain aren't ten different referring domains.

Keep the target scope consistent, too. A whole domain, its subdomains and one exact page can produce different reports. A zero or empty result in one tool doesn't establish that no links exist anywhere.

1. Google Search Console

For your own new site, start with Search Console's Links report. It shows top linked pages, linking sites and linking text for a property you have permission to access.

It's free, but it isn't a substitute for a competitor backlink database.

Google explicitly describes the report as a sample. Tables are limited to 1,000 rows, and links found in the past may remain listed after they've been removed. The report also doesn't specify whether a link is marked nofollow.

That makes it useful for finding sources to inspect, without treating every row as a current, followed placement. Open an important referring page and check it directly.

I'd use this first if the immediate question is simply who is linking to the site you launched. Upgrade elsewhere when the task needs competitor research, different filtering or more usable history, rather than because a small report feels insufficient by itself.

2. Ahrefs

Ahrefs has two free entry points worth separating.

Ahrefs Free, previously called Webmaster Tools, gives access for websites you can verify. Its published Site Explorer allowance is up to 1,000 backlinks and keywords visible at once. That is a display limit, not a promise that a site's total can never exceed it.

The separate public Backlink Checker lets you preview a domain or page you don't own. Don't apply the verified-site allowance to an arbitrary competitor.

For a new website, the free account is worth evaluating before a paid subscription. For competitor work, use the public preview to see whether the available source details answer your question, then check paid limits for exports and historical access.

I wouldn't choose a subscription on Domain Rating alone. A summary metric doesn't replace checking the source page, destination and context of an individual link.

3. Majestic

Majestic is worth comparing when backlink investigation itself is the main job, rather than one feature you occasionally need inside a broader SEO suite.

Lite includes the Fresh Index, Site Explorer, Link Context and referring-domain analysis. Its published allowance includes 5,000 Site Explorer data rows per search. The Historic Index is a Pro feature, so don't assume the entry plan includes the deeper historical workflow.

The pricing page served during research showed pounds sterling: £39.99 monthly, or £399.90 every 12 months, excluding VAT. Keep the annual total in view instead of mistaking the rounded monthly equivalent for a monthly charge.

For a new site with a handful of sources to inspect, free tools may already cover the task. I'd consider Majestic when repeated link research, context or a specific index requirement makes the subscription useful.

Before buying, check the actual report and export allowances you need. “Access to an index” doesn't mean every search returns unlimited rows.

4. SE Ranking

SE Ranking's public Backlink Checker supports domain and exact-URL scopes. When reviewed, the page displayed five free checks remaining that day. Treat that as the published entry-point allowance shown then, not a guarantee of unlimited free reports or exports in every account.

It's useful to try a narrow competitor question before deciding whether you need the wider platform. Look for referring pages, anchors and linked destinations, rather than stopping at a profile total.

The current Core subscription costs $129 monthly or $103.20/month equivalent billed annually. The latter is $1,238.40 for a year by calculation. That buys a broader SEO package, not a standalone backlink lookup.

A trial and a permanent free allowance are different things. Before subscribing, confirm the filters, rows and exports available in the exact access level you're considering. The suite makes more sense if its other tools solve work you already have.

5. Screpy

Screpy's Backlink Checker lets you investigate the selected project or an added competitor. It brings source pages, target URLs, anchors, recorded link attributes and first-seen dates into the same workflow as your website's technical SEO work.

For current public plans, Max includes backlinks and Pro doesn't. Max's regular annual price is $456, equivalent to $38/month paid for the year. It includes 15 projects and 10,000 crawl pages per project. Conditional welcome offers can change checkout pricing; this comparison uses the regular price.

The main tradeoff is scope: the backlink report covers the selected domain, rather than a separately entered page or folder. Loading a report also doesn't freshly test every source URL.

I'd compare it when you need backlink investigation alongside audits and monitoring, rather than backlink research alone. Inspect your account's available report and export limits before planning bulk work. First-seen dates record discovery, and a spam score is a reason to investigate, not proof of a Google penalty.

Pay when a real task hits the limit

Try a small investigation before subscribing. Here's an illustrative workflow for a new site, not a test result:

Check your own domain in a free report you can access. Record the date, scope and whether the number means backlinks or referring domains.
Choose one relevant competitor, if competitor research is part of the job. Use a tool that permits that target and keep the scope consistent.
Collect a short list of useful source pages. For each, note the destination, anchor and observation date. Open important sources to confirm the link and its context.
Write down what stopped you: an unavailable competitor report, too few visible rows, missing history, an export restriction, or a need to repeat the work regularly.

That last line is your reason to pay. Match it to the eligible plan instead of upgrading because another tool displays a bigger total.

For example, if your only task is checking a few launch mentions, a limited report may be enough. If you need repeatable competitor exports, verify that workflow and its limits before committing to a year.

Keep the tools you can explain and use. A backlink count is a starting point for investigation; the useful outcome is knowing which source, destination or next action deserves your attention.

Your First SEO Client? 5 White-Label Reporting Tools to Compare

Mustafa Aydemir — Sat, 07 Nov 2026 06:05:36 +0000

Your first SEO client needs to understand what changed, what you worked on, and what happens next. A report with your logo helps keep that conversation consistent, but the logo is the easy part.

The harder choice is what you're delivering: a PDF you review before sending, a live client portal, or an email that goes out automatically.

These five white-label reporting tools handle those jobs differently. This comparison uses official product and pricing information checked on November 7, 2026, rather than hands-on performance testing.

Disclosure: I'm a co-founder of Screpy, one of the tools below.

Match the tool to the report you owe

A branded PDF, a custom-domain portal and a scheduled email aren't interchangeable deliverables. Decide which one your client expects before comparing subscriptions.

Tool	Pricing basis to compare	Main buying question
AgencyAnalytics	$20 per client/month, billed annually	Do you need a reporting hub for connected marketing accounts?
DashThis Individual	$54 monthly, or $44/month paid yearly; three dashboards and 15 sources	How many separate reports and connected sources will you need?
Swydo	Displayed from €69 monthly, or €62/month billed annually; first 10 sources included	How many integration accounts count toward the source allowance?
SE Ranking	Annual base subscription plus Agency Pack from $69/month, billed annually	Will you use the underlying SEO tools as well as reporting?
Screpy	Reporting access, branding and generation allowance depend on the active plan	Does your account support the branded PDF workflow you need?

These are different packages, not a cheapest-to-most-expensive ranking. Annual equivalents are not monthly payment options. Also separate the cost of collecting data from the cost of presenting it: a reporting integration doesn't automatically include a subscription to the connected SEO tool.

1. AgencyAnalytics

AgencyAnalytics makes sense to compare when the client wants several marketing channels in one place. Its core plan includes automated reporting, unlimited reports and dashboards, and a white-labeled client portal.

The $20 rate is per client, per month, billed annually. One client's base annual cost at that rate is $240, before add-ons or applicable taxes.

Pay attention to the optional native Rank Tracker. The pricing page lists it separately at $41.67/month equivalent per 500 keywords on annual billing. Don't assume the base reporting price buys that tracking allowance too.

Its white-label controls cover branding such as logos and colors, while some advanced options have plan conditions. Check the exact portal, sender and domain setup you intend to use.

I'd shortlist it if your first report needs connected channel data and ongoing client access. If you only owe a reviewed audit PDF, price that simpler requirement first.

2. DashThis

DashThis prices around dashboards and sources. Individual includes three dashboards and 15 sources, so the first question is how you'll organize the client's reports.

One dashboard is a marketing report. If you split the work into several separate reports, count each one rather than assuming “one client” is the billing unit.

The current pricing table lists custom logos, branded themes, removal of DashThis branding, custom domains and custom email across all plans. It also includes automated email dispatch. That's more useful to check than relying on an older comparison that says white labeling starts on a higher tier.

Individual costs $54 month to month, or $44/month paid yearly. The latter comes to $528 for a year by calculation.

This is worth considering when you already have the data sources and need a consistent reporting layer. Check the required integrations and source count before committing to the annual option.

3. Swydo

Swydo takes a different approach: connected data sources drive the price, while clients, users, dashboards and reports are unlimited within that model.

A source means an account connected to an integration. The entry allowance includes 10 sources. As an illustrative budget, one client with two connected accounts uses two sources, not one just because there's one client.

The page served during this comparison displayed euros: €69 monthly, or €62/month billed annually. I've kept that currency instead of treating it as a dollar price. The first 10 sources are included; additional connections can increase the bill.

Swydo includes white-label branding tools, branded PDF exports and client sharing. That combination is useful to evaluate if different clients want different delivery formats without a separate report-count charge.

For your first client, check whether the source allowance leaves room for the actual accounts you'll connect. “Unlimited reports” is helpful, but it doesn't mean unlimited data-source capacity.

4. SE Ranking

SE Ranking's Agency Pack is an add-on to an SEO subscription. It includes white-label platform and report controls, with branded reports that can be delivered automatically or manually.

The important pricing detail is plus the base subscription. Agency Pack starts at $69/month billed annually and is available to annual subscribers. That isn't a standalone $69 reporting account.

The current subscription page lists Core at $103.20/month equivalent on annual billing. Combining those advertised starting rates gives $172.20/month equivalent, or $2,066.40 for a year by calculation, before taxes or other options. Confirm the final configuration at checkout.

That larger commitment may make sense if you also need the SEO research, auditing and tracking workflow. For one client, it deserves a closer look if you already use SE Ranking; it can be excessive if the only missing piece is putting your logo on a report.

5. Screpy

Screpy's report builder takes project evidence into an on-demand PDF. You can reuse templates, select sections and apply agency branding when your plan permits it.

The appeal for technical SEO work is keeping the report close to the audit and tracking evidence. You can explain the issue and next action without turning every dashboard metric into a client deliverable.

There is a purchasing limitation to call out: the public pricing page lists reports as included, but doesn't specify the exact white-label branding entitlement or numeric PDF-generation allowance. Check those in Billing and the report editor before subscribing for this job. Don't interpret “Reports included” as unlimited branded PDFs.

These are snapshots, with source-specific reporting periods. Generating a PDF doesn't make every observation current or give every section the same date range.

Also, white-label templates don't have automatic email delivery, and Screpy MCP doesn't currently expose report records or generation actions. Plan for generating, reviewing and sharing the PDF yourself. Choose another workflow if unattended scheduled report delivery is a requirement.

Check one complete report before you commit

Use a trial or preview to build the report you actually promised. Here's an illustrative first-client check, not a product benchmark:

Use the correct client and domain. Check the cover, portal, exported file and email, whichever surfaces you'll deliver. Keep access limited to the intended client.
Read the dates next to the numbers. If clicks cover one period and an audit comes from an earlier crawl, label both. Don't present them as a synchronized month-end comparison.
Look for missing data. A disconnected account or unfinished crawl isn't a zero result. Fix the connection or explain the limitation.
Add your explanation. State what the evidence shows, what remains uncertain, and the next action you recommend. Separate completed work from proposed work.
Inspect the final output. Open the PDF or client link as the recipient would. Confirm branding, readability, links and the delivery method you intend to use.

Then price that exact setup: the client's connected accounts, separate reports, required collection tools and eligible branding tier. If you want automated delivery, include that requirement from the start.

For a first client, I'd choose the smallest setup that passes this check. The useful report is the one that makes the next conversation clearer, with enough evidence to support it.

5 Local Rank Trackers: What Does the Cheapest Plan Include?

Mustafa Aydemir — Thu, 05 Nov 2026 06:08:51 +0000

A $14 local rank tracker and a $25 grid tracker can be selling very different things. One might check a keyword once a week in a selected city. The other might charge for every point on a map.

That makes the cheapest plan surprisingly easy to misread.

Here are five local rank trackers, the lowest paid tier relevant to their tracking workflow, and the limits worth checking before you subscribe. Prices were checked against official pages on November 5, 2026. This is a documentation-based comparison, not a hands-on ranking benchmark.

Disclosure: I'm a co-founder of Screpy, which is included below.

Compare the allowance before the price

Start with the question you need answered: Where does my business appear for a selected search, or how does visibility change across a neighborhood? A geo-grid checks multiple map points. A saved ranking check doesn't automatically give you that coverage.

These are starting options for different jobs, rather than equivalent baskets:

Tool and relevant entry plan	Price and billing	Main allowance to inspect
Whitespark Local Rank Tracker — Small Business, weekly	$17 monthly, or $168/year ($14/month equivalent)	100 location keywords
Local Falcon — Starter	$24.99 billed monthly	7,500 credits; map points consume credits
BrightLocal — Track, one location	$41 monthly, or $369 billed annually	100 keywords; Local Search Grid up to five keywords
Localo — Single Business	Current annual offer: $39/month equivalent, plus VAT	One active Business Profile; confirm numeric tracking caps
Screpy — Max	Regular $456/year ($38/month equivalent)	15 projects; 50 Map Tracker keywords per project; not a geo-grid

Annual equivalents aren't monthly payment options. Also check whether a limit counts businesses, keyword/location combinations, or individual map points. Those units will determine how quickly you outgrow the entry plan.

1. Whitespark Local Rank Tracker

Whitespark Local Rank Tracker has a useful low-cost entry point if weekly updates answer your question. Small Business includes 100 location keywords, with locations sharing that allowance.

For example, ten keywords tracked in three cities use 30 location keywords. “Unlimited locations” doesn't turn that into unlimited tracking.

The other important choice is frequency. Daily Small Business tracking starts at $25 monthly, or $20/month equivalent when billed annually. Compare that rate if your reporting requires fresh results every day.

Whitespark's separate Local Ranking Grids product shouldn't be assumed to come with this subscription. The tracker covers local and organic search results; the vendor's dedicated grid product is a separate buying decision.

I'd shortlist this for a small keyword set checked across selected locations, especially when weekly history is enough. If you need a neighborhood heatmap, price that specific workflow separately.

2. Local Falcon

Local Falcon fits the question of visibility across map points.

Starter's 7,500 monthly credits are a spending budget. One map pin uses one credit. A 5×5 grid therefore uses 25 point credits per keyword scan.

Unlimited keywords and locations doesn't mean unlimited scans: running searches consumes the allowance. Unused credits expire at the end of the billing cycle. Falcon AI analysis also carries an additional credit charge, so a base grid calculation doesn't include every report option.

Choose your grid size and repeat frequency first. A larger grid can consume the same subscription faster, even when your business count stays unchanged.

3. BrightLocal

BrightLocal Track combines local tracking with audit tools. For one location, its entry plan includes 100 tracked keywords and four competitors, but Local Search Grid supports up to five keywords.

That distinction matters. You can't read “100 keywords” and assume all 100 get grid coverage under the same allowance.

Track also includes local SEO audits, citation accuracy checks and Google Business Profile audits. Those extras may be useful if your next step after spotting a visibility problem is investigating the business's local presence.

The annual payment is $369. BrightLocal displays that as roughly $31 per month; it's an annual commitment, while the monthly option is $41.

For one business that needs both tracking and diagnostic work, this is worth comparing. For an agency, use the location count you actually manage rather than treating the one-location price as the total bill.

4. Localo

Localo Single Business is aimed at managing one active Google Business Profile. The plan lists one optimization seat and brings tracking into a broader profile-management workflow.

The current annual offer shows $39 per month equivalent, plus VAT. Multiplying that rate by 12 gives $468 for a year before VAT. Treat the offer and checkout terms as part of the comparison rather than assuming the same rate applies to monthly billing.

Localo's public pricing text reviewed for this article didn't provide a clear numeric keyword or scan allowance. That leaves a purchasing question unresolved: how much of your particular tracking workload fits?

Before paying, ask for the cap on keywords, map checks and refresh frequency for Single Business. One business included doesn't tell you how many searches you can run for it.

This makes more sense to evaluate if you also want help managing that profile, rather than buying tracking capacity alone.

5. Screpy

For Screpy Map Tracker, Max is the lowest public plan with this feature. Pro doesn't include it. The regular annual Max price is $456, with 15 projects and 50 Map Tracker keywords per project. Conditional welcome offers can change checkout pricing; the table uses the regular rate from Screpy's pricing page.

Map Tracker keeps ranking history using saved business matching and country/language context. It isn't a street-by-street geo-grid. There is no multi-pin heatmap, coordinate selector or device selector. Check the project's entitled refresh frequency rather than assuming daily checks.

The reason to consider the bundle is the website work alongside tracking: Max also includes technical SEO crawling, with 10,000 crawl pages per project. If you need both jobs, compare the combined cost and limits.

If you specifically need neighborhood pin coverage, choose a grid tool. Tracking a position also doesn't automatically fix your website or Business Profile.

Turn your workload into a plan requirement

Here's an illustrative grid budget for one business listing:

A 7×7 grid has 49 points.
Ten keywords require 490 point checks per run.
Four runs use 1,960 point checks.

Under Local Falcon's one-credit-per-pin model, that's 1,960 base point credits. This calculation excludes extra AI analysis and other chargeable options. It's a planning example, not a measured test or a promise about every possible scan setting.

Now change the requirement to daily checks over 30 days. The same grid and keywords need 14,700 point checks. A plan that comfortably covers four runs may fail that requirement without any increase in business locations.

For a useful comparison, write down the business count, keywords, geographic coverage and refresh schedule first. Then check whether the plan can actually deliver that workload.

Whitespark's weekly tracker can suit a small selected-location report. Local Falcon is relevant when you need a configurable grid budget. BrightLocal adds audits with a limited grid-keyword allowance. Localo is worth checking for a one-profile management workflow, once its tracking caps are confirmed. Screpy fits website audits alongside saved Maps ranking history, with the geographic limitations described above.

The cheapest useful plan is the one that covers the question you need answered at the frequency you need it. A lower monthly number won't help if it measures a different job.

5 SEO Tools to Use Alongside Webflow’s Built-In Features

Mustafa Aydemir — Wed, 04 Nov 2026 06:05:58 +0000

Webflow already gives you a lot of SEO control. Before paying for another tool, I'd ask one question: what job is still missing?

Maybe you need to see which queries bring people to a collection page. Maybe you want to inspect backlinks, investigate a slow landing page, or check whether a CMS title rule produced the right result across published items.

Those are useful reasons to add a tool. Buying another place to edit metadata you can already manage in Webflow needs a clearer justification.

These five Webflow SEO tools cover different jobs. This is a comparison based on current documentation, with practical examples of how I'd choose between them. I haven't benchmarked them against the same Webflow project.

Start with what Webflow already includes

Webflow's SEO features include metadata, indexing and redirect controls, automatic sitemaps, and titles and descriptions populated from CMS fields. For a collection, that last capability can save a lot of repetitive editing.

Webflow also has an Audit panel with AI assistance for missing elements such as alt text, titles, descriptions, and schema. Its AI generation consumes credits. The documentation sets eligibility conditions around paid Site plans or Workspaces, user roles, and enabling Webflow AI.

Check those native options before adding another editing app. Then decide what you need outside that workflow: search evidence, backlink research, performance diagnostics, or a separate inspection of the published site.

The five tools below can help with those jobs. You won't need every one for every project.

1. Google Search Console: see which pages earn search attention

Google Search Console is the first place I'd look when a Webflow site is published but the team doesn't know which pages Google is surfacing.

It's a free service with search query, impression, click, and indexing information. You'll need access to the relevant property.

For a CMS collection, examine the pages separately. One article getting impressions doesn't tell you that the whole collection is performing well. Query and page evidence can help you decide which item needs a clearer title, better content, or an indexing investigation.

Then make the appropriate change in Webflow. A report showing low clicks isn't proof that the metadata alone caused the problem, so avoid rewriting the entire collection based on one number.

Best fit: understanding your own Google Search presence. It supplies evidence that a publishing settings panel can't provide on its own.

2. Ahrefs Free: inspect your site's backlinks and organic footprint

Ahrefs Webmaster Tools is now called Ahrefs Free. That matters if you're following an older Webflow tutorial and wondering whether it's still the same offer.

The free access is for verified websites. It includes Site Audit and Site Explorer insights into backlinks and organic search. The current page lists 5,000 crawl credits per verified project per month, plus up to 1,000 backlinks or keywords visible at once. Those are different limits from a simple per-crawl URL cap.

For a Webflow content site, I'd use the backlink view to investigate which published resources attract links. That can inform what deserves maintenance or a clearer place in your site's navigation.

Treat the reports as the tool's available dataset, rather than a complete inventory of the web. Free verified-site access also doesn't mean unrestricted research on every competitor.

Best fit: getting useful own-site research without immediately paying for a broader suite. You still edit the content and linking structure in Webflow.

3. PageSpeed Insights: check the experience behind the design

PageSpeed Insights is useful when a Webflow page looks good in the Designer but feels slow on a phone. Test a representative collection item as well as a heavily designed landing page; they may load very different assets.

The free web tool provides mobile and desktop diagnostics. Google's documentation distinguishes lab results from real-user field data covering the previous 28 days.

Check the scope of the field report. It may describe the page, the broader origin, or have insufficient data. A new collection item won't necessarily have its own real-user assessment yet.

Use the diagnostics to decide what to investigate in the Webflow build, such as large media or added scripts. Keep the URL and device category consistent when comparing runs. A single score doesn't identify the cause of a change.

Best fit: finding performance questions worth investigating before adding more effects, embeds, or assets. Hosting features don't make every page design equally light.

4. Screpy: review technical findings across the published site

I'm a co-founder of Screpy, so that's my connection to this entry.

Its SEO crawler helps you review technical findings such as metadata, links, and indexability across public URLs. Alongside Webflow, its role is inspecting the published result and helping you work through affected pages.

For example, if several collection items have the same unexpected title, check the shared CMS mapping before editing each item. A list of affected URLs is useful when it helps you identify one repeatable correction.

Pro's regular annual price is $192, with five projects and 5,000 crawl pages per project. Annual billing is paid upfront. Welcome discounts have conditions; subscriptions renew automatically, and trials become paid unless cancelled before they end.

Best fit: a project workflow for returning to technical issues as the Webflow site grows. Screpy isn't a native Webflow editing integration, and findings don't automatically change your CMS fields or publish fixes.

5. Screaming Frog: investigate published CMS output in detail

Screaming Frog SEO Spider is a desktop crawler for technical investigations. It can help you inspect titles, canonicals, response codes, and redirects across the published Webflow site.

I'd choose it when I want a focused URL inventory and a closer look at a specific pattern. After changing a collection's URL structure, for example, check both where old links lead and whether navigation uses the intended current URLs.

The free version crawls up to 500 URLs. Count the whole reachable site, including collection items and archives, when deciding whether that covers your investigation. The vendor page currently displays a paid licence at €245 per year; check the currency and checkout terms for your location.

Best fit: hands-on desktop audits. It overlaps with other crawlers, so choose based on your workflow and required coverage. Running multiple audits isn't useful unless the extra evidence answers a real question.

Choose the missing job before the subscription

Tool	Useful addition to Webflow	Entry cost or limit
Google Search Console	Actual Google query and page evidence	Free; property access required
Ahrefs Free	Verified-site backlink and organic search insights	Free; 5,000 monthly crawl credits per project; visibility limits apply
PageSpeed Insights	Performance diagnostics for published pages	Free; real-user data may be unavailable
Screpy	Project-wide technical findings and follow-up	Pro regular $192/year; five projects, 5,000 crawl pages/project
Screaming Frog	Focused desktop crawl investigations	Free 500 URLs; paid page displays €245/year

These are different allowances and currencies, so the table isn't a cheapest-to-most-expensive ranking. Prices were checked November 4, 2026.

Here's a practical Webflow example. Suppose your collection's SEO title should combine the item name and the site name. Pick several published items, including one with a long name and one with optional fields left empty. Check the actual titles and intended canonical URLs with your chosen crawler. If the pattern is wrong across the sample, correct the shared rule in Webflow, publish, and inspect again. A sample helps diagnose the mapping; it doesn't certify every item.

I'd start with Search Console and the free diagnostics needed for the current problem. Add a paid workflow when its coverage or the repeated work makes sense. Let Webflow handle the publishing controls it already provides, and use outside tools to answer the questions you still have.

Beyond Your WordPress Plugin: 5 Tools for Technical SEO

Mustafa Aydemir — Tue, 03 Nov 2026 06:03:11 +0000

Your WordPress SEO settings can look right while the public page still has a problem. A theme update changes the markup. A permalink change leaves old links behind. A new script makes the mobile experience slower.

An SEO plugin is useful for controlling what your site should output. For WordPress technical SEO, I'd also keep a few tools that check what actually reaches the outside world.

These five cover different questions: what a crawler finds, what Google has indexed, how a page performs, whether its structured data is eligible for supported rich results, and what needs another technical review.

This comparison is based on current product documentation, not a benchmark on a test WordPress installation. The aim is a small, useful inspection workflow after a change—not another pile of plugins to maintain.

Which technical SEO tool answers which question?

Tool	Use it for	Cost reference	What a good result doesn't prove
Screaming Frog SEO Spider	Site-wide links, responses, redirects and metadata	Free up to 500 URLs; paid £199/year	Google has indexed those URLs
Google Search Console	Google's indexed record and live URL checks	Free	A successful live test guarantees indexing
PageSpeed Insights	Performance diagnosis on mobile and desktop	Free web tool	One lab run represents every visitor
Rich Results Test	Google-supported structured data checks	Free web tool	Google will display a rich result
Screpy	External technical SEO review across a project	Pro regular annual price: $192	The report has changed your WordPress site

Prices checked November 3, 2026. Annual prices mean annual billing, and the currencies aren't converted here. Confirm taxes, licence scope, and any offer conditions on the vendor's current page.

1. Screaming Frog: investigate changes across the site

Screaming Frog SEO Spider is a desktop crawler for Windows, macOS, and Linux. It helps you examine response codes, redirects, titles, and canonical tags across URLs instead of checking every WordPress editor screen.

I'd reach for it after changing permalinks or navigation. The question is concrete: do internal links reach the intended destination, or are they pointing to broken pages and unnecessary redirects?

Look for shared patterns before assigning individual fixes. If every link in one menu points through an old path, updating that menu may be more useful than editing unrelated posts.

The free version crawls up to 500 URLs. Archives, pagination, and other reachable URLs count too; 400 posts doesn't necessarily mean a complete crawl fits. The paid licence is listed at £199 per year.

Choose it for: a focused crawl investigation. A clean crawl only describes the URLs and conditions inspected. It isn't Google's indexing decision or proof that an undiscovered page has no issues.

2. Google Search Console: separate the live page from Google's record

Google Search Console answers a different question from a crawler: what does Google report about this URL? You'll need access to the relevant site property.

The URL Inspection documentation distinguishes the indexed version from a live test. That matters when you've just removed an unintended indexing restriction or corrected a canonical setting.

Use the live test to investigate whether the current page might be indexable. Use the indexed information to examine Google's existing record, including the Google-selected canonical when available. The live test cannot predict that canonical selection.

Don't mark a release as fully processed by Google just because the live test succeeds. Record which version you inspected and what remains to be checked later.

Choose it for: Google-specific indexing evidence. It's free, but it doesn't edit your WordPress settings, and an indexing request is not a guarantee of inclusion.

3. PageSpeed Insights: diagnose the page visitors receive

PageSpeed Insights is useful after adding a page builder block, changing a theme, or introducing a third-party script. Test the affected page rather than assuming the homepage represents the whole site.

Google's documentation separates controlled lab diagnostics from real-user field data. Lab results help you investigate the current page. Available field data describes a historical collection window of the previous 28 days.

Those aren't interchangeable release checks. A lab run can help you investigate a new problem now; the field view won't instantly become a clean measurement of your latest deployment. Check whether the displayed field data applies to the URL or the broader origin. Some pages don't have enough real-user data for a field assessment.

For a useful comparison, keep the tested URL and device category consistent and record what changed. A single score moving up or down isn't enough to identify the cause.

Choose it for: free, page-level performance diagnosis. It provides evidence to investigate; it doesn't configure your cache or optimize your theme for you.

4. Rich Results Test: inspect the structured data your site publishes

Google's Rich Results Test is useful after changing a theme or a plugin setting that affects structured data. Test the public URL so you're checking the generated output, rather than only the values entered in WordPress.

For example, after changing an article template, inspect which supported items the tool detects and whether it reports errors. Then compare the detected information with the visible page. Passing a technical check doesn't make an incorrect author or misleading detail accurate.

Google describes this tool as a check for Google-supported rich results, not a universal validator for every Schema.org type. It also explicitly says correct markup doesn't guarantee rich-result display.

Choose it for: a free check of supported structured data after an output change. It won't repair conflicting theme and plugin output, or tell you that your entire site's technical SEO is finished.

5. Screpy: keep external technical review in your maintenance routine

I'm a co-founder of Screpy, so that's my connection to this recommendation.

Its SEO crawler helps you review technical findings and affected URLs across a public website, including metadata, links, and indexability. For WordPress maintenance, the useful habit is returning to those findings after changes, rather than treating the launch audit as permanent evidence.

Give each fix a simple record: affected URL, expected output, change made, and follow-up result. If a problem appears across several pages, investigate the shared source before editing them individually.

Pro's regular annual price is $192, with five projects and 5,000 crawl pages per project. That is annual upfront billing. Conditional welcome offers are separate; subscriptions renew automatically and a trial becomes paid unless cancelled before it ends.

Choose it for: keeping project-wide technical review part of ongoing maintenance. It complements your WordPress tools; it isn't a native WordPress editor and doesn't automatically apply theme or plugin fixes.

Match the tool to the WordPress change

Here's an illustrative release checklist. It isn't a claim that every update needs every check.

Change or symptom	Start here	Evidence to record	Still unknown
Permalinks or navigation changed	Screaming Frog	Old link, response, final destination	Whether Google has reprocessed the change
Important page missing from Google	Search Console	Indexed record and separate live result	Whether or when Google will index it
New script or heavier page layout	PageSpeed Insights	URL, device, lab diagnostics, field-data scope	Impact on every real visitor
Theme or structured-data output changed	Rich Results Test	Detected supported items and errors	Whether a rich result will appear
Technical findings need follow-up	Screpy	Affected URLs, changes and repeat-review findings	Problems outside the inspected scope

For a small WordPress site, I'd begin with the free checks that answer the current problem. Add paid crawl capacity or a project workflow when its limits or the repeated work justify the cost. You don't have to buy both crawler options to start.

Keep the SEO plugin that already handles your publishing settings well. Use these tools to verify the result, then fix the actual source of the problem. That gives each tool a clear job—and gives you a better stopping point than “the score turned green.”

Hundreds of Product Pages? 5 WooCommerce SEO Tools to Consider

Mustafa Aydemir — Mon, 02 Nov 2026 06:13:50 +0000

A WooCommerce catalog can have hundreds of products and still be manageable. The painful part is discovering that the same bad title template, missing product detail, or canonical mistake affects an entire collection.

That's the problem I'd use WooCommerce SEO tools to solve first: make good settings repeatable, then check what the store actually publishes.

Start with a simple product, a variable product, a category, and a filtered URL. If those behave differently, editing every product description won't fix the underlying rule.

These five tools cover different parts of that workflow. Rank Math and Yoast work inside WordPress. Screaming Frog and Screpy inspect the public site. Search Console shows Google's indexing evidence. This is a documentation-based comparison, not a claim that I've benchmarked them on the same store.

Quick comparison

Tool	Main job	Cost reference	Important boundary
Rank Math	WooCommerce SEO settings in WordPress	Free version available	Advanced product features require PRO
Yoast WooCommerce SEO	Product SEO and catalog templates	$178.80/year, excluding VAT	Paid WordPress product; verify licence scope for your stores
Screaming Frog SEO Spider	Desktop technical crawling	Free up to 500 URLs; paid £199/year	URLs aren't the same as product records
Screpy	External technical SEO review	Pro regular price: $192/year	Five projects; 5,000 crawl pages per project
Google Search Console	Google indexing and search evidence	Free	Requires access to your site's property

Prices checked November 2, 2026. Dollar and pound prices are shown in their original currencies, without exchange-rate comparisons. Annual subscriptions require the annual payment; promotional offers and taxes can change the checkout total. Check the linked vendor pages before buying.

1. Rank Math: start with free WooCommerce controls

Rank Math makes sense when you need SEO settings where you already manage products. Its free version includes a WooCommerce settings module, so you can evaluate the basic workflow before paying for advanced features.

The useful buying question is which product fields and checks your catalog actually needs. Rank Math's free-versus-PRO WooCommerce comparison places GTIN functionality and dedicated product content analysis in PRO. Don't assume every WooCommerce feature mentioned in a review belongs to the free plugin.

For a larger catalog, test your chosen settings on a few representative product types before applying them broadly. Check the resulting public page as well as the editor screen.

Best fit: a store starting with free in-WordPress controls. An external crawl still has a separate job: finding problems across the URLs visitors and search engines can reach.

2. Yoast WooCommerce SEO: a paid catalog editing workflow

Yoast WooCommerce SEO is worth considering when your work centers on keeping product information and SEO settings consistent inside WooCommerce.

Its current product page describes catalog templates, product-specific analysis, structured product data, and AI-generated image alt text that you review before applying. The listed price is $178.80 per year excluding VAT. Use that current product page rather than assuming an older add-on price still applies.

Templates are useful when products share a predictable structure. Exceptions still need attention: a variable product, a bundle, and a discontinued item may need different treatment. Review generated suggestions against real product details before saving them across a collection.

Best fit: a team that values a paid product editing workflow. If your existing SEO plugin already covers your requirements, identify a missing capability before planning a migration. Treat Yoast and Rank Math as alternatives for the main SEO-plugin role.

3. Screaming Frog SEO Spider: count URLs before choosing a crawl limit

Screaming Frog SEO Spider is a desktop crawler for investigating technical issues across a site. It can help you review response codes, redirects, page titles, and canonical tags.

The free version crawls up to 500 URLs. That's an important distinction for WooCommerce: your catalog count doesn't include every category, pagination page, or parameter URL a crawl might discover. A store with fewer than 500 products can exceed the free crawl allowance.

The paid licence is listed at £199 per year. Decide whether you need it based on crawl coverage and required capabilities, rather than product count alone.

For a catalog audit, look for patterns by URL type. Repeated titles across a category may point to a template problem; redirects appearing throughout navigation may point to outdated internal links. Those patterns can make the fix list much smaller.

Best fit: focused technical investigations from your computer. The crawl supplies evidence; changes still happen in your store or code.

4. Screpy: review technical issues across the public store

I'm a co-founder of Screpy, so that's my connection to this entry.

Its role here is external technical SEO analysis. The SEO crawler helps you investigate issues such as metadata, links, and indexability across the public website. It complements the work you do in your WooCommerce editor.

For a growing catalog, the practical question is whether a finding affects one product or an entire URL pattern. Reviewing affected pages together helps you decide whether to edit a product, change a shared template, or investigate navigation.

The pricing page lists Pro's regular annual price at $192, covering five projects and 5,000 crawl pages per project. That's a prepaid annual subscription. Conditional welcome offers are separate, and subscriptions renew automatically. A trial becomes paid unless cancelled before it ends.

Best fit: reviewing technical findings across your store over time. Screpy doesn't act as a native WooCommerce product editor, and a crawler report doesn't automatically change your theme or fix your catalog.

5. Google Search Console: check Google's indexing evidence

Google Search Console is free and belongs in this workflow regardless of which editing plugin or crawler you choose. You'll need access to the store's property.

Use URL Inspection when an important product or category isn't appearing as expected. It provides information about Google's indexed version and a separate live test of whether the current URL might be indexable.

That distinction matters after a template fix. A successful live test doesn't prove Google has reprocessed the change or indexed the page. Compare the available indexed information with your current public output before declaring the issue resolved.

Best fit: checking what Google reports for priority URLs. It doesn't replace catalog editing or a comprehensive crawl, and requesting indexing doesn't guarantee inclusion.

Choose a small stack, then check the templates

I'd choose one main SEO plugin, add a crawl method when I need broader coverage, and use Search Console for Google's evidence. There isn't much value in buying overlapping tools before identifying the bottleneck.

Write down your expectations for a few real URLs first:

Sample URL	What to check
Simple product	Unique title, accurate product details, intended canonical
Variable product	Variant choices and published price/availability make sense together
Product category	Useful category content, navigation, intended indexability
Filtered category	Whether this particular filter should be indexed and which canonical is intended

There's no universal rule that every filtered page should be indexed or excluded. Make that decision for your store before using a tool to enforce it.

Check those samples, correct the shared rule where appropriate, then review affected URLs again. A clean sample isn't proof that every product is correct, but it gives you a practical starting point for a wider audit.

For hundreds of product pages, that's where these tools become useful: helping you find the shared problem and verify the change, instead of giving you hundreds of isolated tasks.