Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect HTTP Status Code for Deep Pagination Limit #132

Open
mslinnea opened this issue Feb 28, 2025 · 1 comment
Open

Incorrect HTTP Status Code for Deep Pagination Limit #132

mslinnea opened this issue Feb 28, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@mslinnea
Copy link
Member

Description of the bug

Currently, the Disable Deep Pagination feature returns an HTTP 400 (Bad Request) status code. This is flagged by SEO tools like Screaming Frog because search engines may interpret this as a client-side error, which can lead to indexing issues and wasted crawl budget.

Instead of an HTTP 400 error, the site should return an HTTP 410 (Gone) status instead. A 410 is a signal that the page is intentionally removed and won’t return. This will prevent the search engine from trying to crawl it or flagging it as a 404.

Steps To Reproduce

  1. Navigate to a page exceeding 100 in pagination.

Additional Information

File that needs changing is https://github.com/alleyinteractive/wp-alleyvate/blob/main/src/alley/wp/alleyvate/features/class-disable-deep-pagination.php

@mslinnea mslinnea added the bug Something isn't working label Feb 28, 2025
@mboynes
Copy link
Contributor

mboynes commented Feb 28, 2025

I would say it's also worth adding rel="nofollow" to the deep pagination links

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants