Product

A complete diagnosis of the site, the Google Business Profile and Bing, with proof for every number.

Who it's for

Agencies, consultants and companies that need to show what is wrong with a site and follow the fix.

Help

Straight answers, a real report to explore and real people on the other side.

Try it free
Search

What keeps Google from crawling and indexing your site, page by page

Technical SEO is the set of conditions that let Google crawl, understand and index a site: status codes, redirects, canonical tags, sitemaps and the tags on each page. Path Ranker walks your site like a search engine, following internal links, and checks status codes, redirects, canonical tags, robots.txt, sitemaps, hreflang and the tags on every page. Each problem comes with the URL, the evidence and a command to repeat it.

How it works

01

A crawl like a search engine

It starts at the home page and follows internal links up to the page limit of your plan. It reads robots.txt, finds the sitemap and looks for common pages such as contact, about and privacy.

02

Every page and every link

It records status, depth, canonical, noindex, title, description, H1 and hreflang. It tests the internal links the crawl did not open and a sample of the external ones. On a sample of pages, it opens a real browser and compares the result with the HTML received.

03

Problems with proof

You get the site health, the errors, warnings and notices of each page and the URL table to download as CSV. Every finding says what to fix and includes the command to check it.

What it checks

Crawl and status codes

The status of every page read (200, a 4xx error, a 5xx error or no response), its depth in clicks from the home page and how many internal links point to it.

Broken and redirected links

Up to 150 internal links the crawl did not open and up to 40 external ones, tested without following redirects, which are listed with their target. Only 404, 410 and 5xx count as broken; 401, 403 and 429 are marked as not verifiable.

robots.txt and sitemaps

robots.txt read with Google’s longest-match rule, including a block of the whole site. The sitemap, declared or at the usual addresses, with 12 URLs tested, the newest lastmod date and the crawled pages missing from it.

Indexability and canonical

noindex in the meta robots tag and in the X-Robots-Tag header, a missing canonical or one pointing to another URL, soft 404s (an address that does not exist but answers 200) and the site served on its bare IP.

Tags on every page

Missing, duplicate, long or short titles and meta descriptions; missing or multiple H1s; viewport, lang, Open Graph, Twitter Card, favicon, doctype, charset and image alt text.

hreflang

Valid codes (pt_BR and en-UK are rejected), return links between versions, self-reference, x-default and alternates that do not answer 200, are noindex or have a canonical pointing elsewhere.

JavaScript and rendering

On up to 5 pages, a real browser builds the page and the result is compared with the HTML received: noindex or canonical added or changed by script, a changed title, and H1s, text and links that only exist after JavaScript runs.

Site audit

The health score (the share of pages without errors), exact and near-duplicate content, pages competing for the same term, URLs with capitals, underscores, parameters or over 115 characters, and generic link text such as "click here".

What it does not do

  • It does not change your site: it reads public pages from the outside, like a search engine. Firewalls and bot protection services can block the crawl; if that happens, allow Path Ranker or switch the user agent in the advanced crawl settings.
  • The crawl follows links from the home page. A page with no internal link at all only shows up through the sitemap, and the list of sitemap pages without links only appears when the crawl reaches the whole site within your plan’s limit.
  • The real-browser comparison uses a sample of up to 5 pages, not the whole site. Subdomains count as separate sites and are not crawled.
  • Only Search Console can say whether a page is actually in Google’s index. That data comes from the Search Console integration, with your account connected.

Which plans include it

Free: one analysis per sign-up, home page only (robots.txt, sitemap and the page tags), without the real-browser comparison; it shows the problems, not how to fix them. Starter: up to 60 pages per domain. Pro: up to 200. Enterprise: up to 500. On paid plans, the SEO and structure group can run on its own. Scheduled analyses: monthly on Starter, weekly on Pro and daily on Enterprise (for up to 25 domains; the rest weekly).

See pricing

Frequently asked questions

  • Up to your plan’s limit: 60 per domain on Starter, 200 on Pro and 500 on Enterprise. Free reads the home page only. You choose the number of pages for each analysis.
  • Yes. On up to 5 pages, a real browser builds the page and the report shows what only exists after the script runs: text, links, title, canonical or noindex. That is what crawlers that do not run JavaScript miss.
  • Yes, in the domain’s advanced crawl settings on paid plans: follow only some paths, skip others, limit the depth in clicks, use another user agent (such as Googlebot), log in to a staging site with a username and password, and extract a field from every page with a CSS selector, XPath or a regular expression.
  • Only when it answers 404, 410 or a 5xx error. Answers of 401, 403 or 429, common on sites that block bots, and no answer at all are shown as not verifiable, not as broken.
  • Every finding includes the URL and a command. For links and redirects, for example: curl -sS -o /dev/null -w "%{http_code} %{redirect_url}" URL, which prints the status and the target. Anyone can run it and get the same result.

Other features

Crawl your site like a search engine

Paste the address and see, page by page, what gets in the way of crawling and indexing.

Try it free