Make sure important links have not disappeared
Check that navigation, related content, and calls to action still appear after rendering, so important pages keep their internal entry points.
Free Googlebot link crawl check
Googlebot Spider Simulator
See the rendered links a Googlebot Smartphone-style crawl can discover - then check duplicate targets, follow directives, and page signals that can affect internal link equity flow.
After publishing, make sure Googlebot can see your important pages and links
A page can look normal in your browser while Googlebot sees different content or links. Check one public URL after JavaScript renders to find missing, repeated, or accidentally restricted links before they become an SEO problem.
See whether repeated links are only noise
Group matching destinations to separate expected navigation repeats from redundant links worth cleaning up.
Catch nofollow in the wrong place
Review nofollow, ugc, and sponsored markers together so important internal links are not accidentally restricted.
When a quick link check saves you time
After publishing or redesigning a page
Make sure navigation, related content, and calls to action still create the paths you intended.
When an important page is hard to find
Check whether the page still receives internal links and visible anchor text after JavaScript renders.
Before you promote new content
Confirm that the mobile-rendered page exposes the key content and links visitors and crawlers need to find.
In 3 minutes, make sure publishing has not hidden your important links
Google primarily understands pages through a mobile crawler. This tool uses a Googlebot Smartphone-style mobile rendering environment to check a public page, giving you a practical view of the content and links a modern mobile-first SEO and GEO workflow needs to inspect.
- 1Paste a public page URL you just published, updated, or need to diagnose.
- 2Simulate how a Googlebot Smartphone-style mobile renderer loads the page.
- 3Check that key content, internal links, and nofollow directives still appear as intended.
Mobile-first indexing is the default for most websites. That makes a mobile rendering check a more useful starting point than relying on a desktop browser alone when you investigate SEO or AI-search visibility issues.
What the follow status does - and does not - mean
Do Follow means the rendered link has no rel="nofollow" token. It does not prove that Google transfers a particular amount of PageRank or link equity.
No Follow means the rendered link includes a nofollow token. Google treats nofollow as a hint and can still make its own crawl and ranking decisions.
The report does not prove that Google has crawled, indexed, or ranked the page. Pages behind sign-in, CAPTCHAs, access controls, or bot protection may not render.
This is a Googlebot Smartphone-style rendering simulation, not a Google Search index inspection or a measurement of PageRank. A Do Follow result means the page does not declare rel="nofollow" for that link; it does not guarantee that Google will crawl the target or assign a fixed amount of link equity.
FAQ
Does Do Follow mean a link passes PageRank?
Not by itself. Do Follow means the rendered link does not use rel="nofollow". Google considers many other signals before it crawls a target or uses a link in ranking, so this tool reports the page-level directive rather than a PageRank value.
What does a No Follow result mean?
It means the rendered link includes a nofollow token in its rel attribute. Google treats nofollow as a hint, so it is useful for auditing page markup but does not predict an exact crawl or ranking outcome.
Why are duplicate link URLs grouped together?
A destination often appears in navigation, body copy, and the footer. The report groups matching rendered URLs, shows the number of occurrences, and keeps the available anchor text so you can audit the target without duplicate rows.
Why use a Googlebot Smartphone simulation?
Google uses mobile-first indexing for most websites. A smartphone rendering profile is therefore a practical baseline for checking the links and content a mobile crawler-style browser receives after JavaScript runs.
Does this match Googlebot exactly?
No. The tool models a Googlebot Smartphone rendering environment, while Google controls its own crawl schedule, rendering queue, location, resource policies, and index decisions. Treat this report as diagnostic evidence, not a Google Search inspection.
Enter a public URL to see the rendered link inventory, follow directives, repeated destinations, and the page context behind them.