HTTP 405 Method Not Allowed
405 Method Not Allowed means the server recognises the request method but the target resource does not support it — for example a POST to a GET-only page. For crawlers, which issue GET (and sometimes HEAD), a 405 usually means the route does not allow GET, often a misconfiguration on a URL that should serve a page.
What 405 means
405 Method Not Allowed is a client-error status saying the server knows the request method but the target resource does not support it. The response must include an Allow header listing the methods the resource does accept.
It is distinct from 404 (no such resource) and 501 (method not implemented at all): with 405 the resource exists, it just will not accept that method.
Why crawlers see 405
Search and AI crawlers fetch with GET, and sometimes probe with HEAD. If a page route is configured to allow only POST, or if HEAD is not handled, a crawler can receive a 405 on a URL you intend to be indexable.
The usual causes are a route that only declares POST handling, an API endpoint exposed where a page is expected, or a framework that does not respond to HEAD. The fix is to allow GET (and ideally HEAD) on any URL meant to be crawled, and to keep method-restricted endpoints out of crawl paths.
- 405 = resource exists but method not allowed
- Allow header lists the accepted methods
- Page routes should accept GET and HEAD for crawlers
Operator checklist
Confirm indexable URLs accept GET and HEAD and return an accurate Allow header on 405. Investigate 405s a crawler receives — they usually mean a route rejects GET/HEAD. Keep POST-only action endpoints out of internal links and sitemaps.
How it appears in analytics and logs
A 405 means the method is not allowed for that resource. For a crawler issuing GET or HEAD, a 405 indicates the route rejects those methods — typically a routing or framework misconfiguration on a URL meant to be a page.
Diagnostic use case
Diagnose why a crawler receives 405 on a URL that should be GET-able, and confirm page routes allow GET and HEAD.
What WebmasterID can help detect
WebmasterID can surface URLs where crawlers receive 405s, helping you find page routes that wrongly reject GET or HEAD requests.
Common mistakes
- Page routes that handle only POST, so crawler GETs get 405.
- Not handling HEAD requests, which some crawlers send.
- Omitting the Allow header from a 405 response.
Privacy and accuracy notes
Status codes carry no personal data. WebmasterID reports 405 patterns for crawler traffic without exposing individual visitors.
Related pages
- HTTP 501 Not Implemented
501 Not Implemented means the server does not support the functionality required to fulfil the request — typically an HTTP method it does not recognise or handle at all. It is a server-side error distinct from 405, where the resource exists but rejects a specific method. For crawlers it is an uncommon, server-level failure.
- HTTP 201 Created and crawlers
201 Created means the request succeeded and resulted in one or more new resources being created, typically in response to a POST or PUT. It is a success status tied to writes, so it is rare for the GET requests crawlers issue. Seeing 201 in crawler logs usually points at an API or form endpoint being fetched, not a normal page.
- Website observability
Spot URLs where crawlers receive client-error responses.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.