"Blocked due to access forbidden (403)": what it means and how to fix it
The server turned Google away with 403 Forbidden.
A setting blocks it
What it means
The server would not show the page to Google. Bot blockers and firewalls often cause this.
Which of your pages have this problem? Find out for free.
Get my free reportCommon causes
- A firewall or bot blocker blocks Google.
- File settings on the server.
How to fix it
- Let verified Google crawlers through your firewall or bot blocker.
- If the page is private, take it out of your sitemap.
How to find these pages
In Search Console, open Indexing > Pages and click the "Blocked due to access forbidden (403)" row. Search Console shows up to 1,000 example pages. CrawlCoach checks up to 50,000 pages per site and sorts them by reason, so you know which pages to fix first.
Which of your pages have this problem?
Sign in with Google. CrawlCoach checks up to 500 pages for free and shows the fix for each problem.
Get my free reportFree for up to 500 pages. No card needed. Sign in with the Google account you use for Search Console.