410 Block Duplicate URLs
Budget: $8 – $15 USD
I’m running the site on an Nginx server and need a clean, permanent way to return HTTP 410 for roughly 15 000 junk URLs. All of these unwanted addresses share a clear pattern: they repeat category terms and always include the word “filter”, e.g.
/ shop/?stock_status=in_stock&filter_cat=
Legitimate product and category URLs never contain “filter”, so they must stay fully accessible. The task is therefore to create an Nginx rewrite rule set (not .htaccess) that:
• Matches every current and future URL containing “filter” (and similar duplicate-patterned segments)
• Responds with 410 Gone, removing them from the index permanently
• Leaves every normal URL untouched
Deliverables
1. A vetted Nginx configuration snippet I can drop into my server block.
2. Brief implementation notes covering where to place the code, how to test, and a simple rollback step.
3. Confirmation that the rule returns 410 in both desktop and mobile crawls and that Google Search Console stops surfacing the duplicates.
Please attach a concise proposal showing how you’ll detect the patterns, the exact rewrite or map logic you’ll use, and any past experience handling large-scale URL pruning on Nginx.
/ shop/?stock_status=in_stock&filter_cat=
Legitimate product and category URLs never contain “filter”, so they must stay fully accessible. The task is therefore to create an Nginx rewrite rule set (not .htaccess) that:
• Matches every current and future URL containing “filter” (and similar duplicate-patterned segments)
• Responds with 410 Gone, removing them from the index permanently
• Leaves every normal URL untouched
Deliverables
1. A vetted Nginx configuration snippet I can drop into my server block.
2. Brief implementation notes covering where to place the code, how to test, and a simple rollback step.
3. Confirmation that the rule returns 410 in both desktop and mobile crawls and that Google Search Console stops surfacing the duplicates.
Please attach a concise proposal showing how you’ll detect the patterns, the exact rewrite or map logic you’ll use, and any past experience handling large-scale URL pruning on Nginx.