SEO

403

Also called Forbidden, HTTP 403

The response a server gives when it understands a request but refuses to serve the content.

Quick facts: 403

Category
SEO
Also called
Forbidden, HTTP 403
Level
Intermediate
Affects
Crawlability, indexing, page rendering
Where to see it
Search Console URL Inspection (live test), server and firewall logs, Screaming Frog
In this article4
  1. How a 403 works
  2. Why a 403 matters
  3. Common mistakes with 403s
  4. How to act on it

How a 403 works

A 403 is a refusal, not a mistake. The address is valid and the content usually exists; the server has simply decided this visitor is not allowed to have it. That decision can be made in several places — file permissions on the host, a security plugin, a firewall in front of the site, a rule at your CDN, or a login-only area behaving exactly as intended.

The important detail is that the refusal is aimed at whoever asked. A page can serve normally to you and be refused to somebody else, because the rule is looking at an address, a country, a device or the name a client gives when it introduces itself. Crawlers announce themselves plainly, which makes them the easiest thing in the world to block by accident.

Why a 403 matters

If a search engine is refused, it gets no content. A page that is already indexed will hold on for a while and then fall out, and a new page will never enter at all. Nothing about the site looks broken while this happens — the pages load perfectly in your own browser, which is precisely why it can run for weeks.

Refusals on assets are just as damaging and even harder to spot. If the HTML is served but the stylesheet, script or image files are refused, crawlers and real visitors see a broken skeleton of the page. On sites hosted abroad and served to Nepal through aggressive security rules, blocking by country or by network is a real cause, and the owner sitting in the same country as the server never sees it.

Common mistakes with 403s

Blocking bots wholesale to save server load is the most common. It works, in that the load drops, and it also removes the site from search. Any blocking rule needs an exception for verified search engine crawlers, and it needs testing rather than assuming.

Next is leaving password protection on a staging environment after it becomes production, so the live site refuses everyone but the team. Then there is treating a 403 as if it hid a page from search deliberately — it does not do that reliably, it simply denies access, and a URL that is refused can still be known about from links elsewhere. If you want a page kept out of the index, say so with a noindex instruction on a page that can actually be fetched.

How to act on it

Reproduce the refusal as a crawler rather than as yourself. The live test in Search Console’s URL Inspection shows what Google receives, and a crawl run with a search engine user agent will surface refusals across the whole site. Compare that with what your own browser sees; a difference between the two is the finding.

Then trace the layer responsible by working inwards: CDN rules, then the firewall or security plugin, then server configuration, then file permissions. Each of those keeps its own log, and the blocked request will be in one of them. Once fixed, add a scheduled crawl so an accidental refusal is caught by monitoring rather than by a client, and treat crawler access as a standing item in your technical SEO checks alongside your robots.txt rules.

Do and do not

Do

  • Allow verified search engine crawlers through security rules
  • Test the site as a crawler, not only as yourself
  • Remove staging password protection before launch

Do not

  • Block bots wholesale to reduce server load
  • Use a refusal to hide a page from search
  • Forget that blocked scripts and images break rendering

Questions people ask about this

Why does a page work for me but return 403 for Google?

Because the refusal depends on who is asking. Security rules commonly block by network address, country or the name a client gives when it connects, and crawlers identify themselves openly. Your browser passes the rule and the crawler does not. Use the live test in Search Console's URL Inspection to see exactly what Google receives.

Can I use a 403 to keep a page out of search results?

It is the wrong tool. Refusing access stops the content being read, but the address can still be discovered through links on other sites and may appear with no description. To keep a page out of the index properly, let it be fetched and mark it noindex, or put it behind a genuine login if it is private.

How do I find which rule is causing a 403?

Work from the outside in. Check your CDN or proxy rules first, then any firewall or security plugin, then the web server configuration, then file and folder permissions on the host. Each layer keeps its own log of blocked requests, and the request you are chasing will appear in exactly one of them with a reason attached.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.