Prompt
Why did my scraping pipeline break after a site redesign?
Latest observation
Oct 18, 2026
OpenAI APIWeb search: off
Site redesigns often break scraping pipelines because scrapers are usually tied to the site’s old structure, not just its content. Common causes:
- HTML changed: CSS classes, IDs, tag hierarchy, or attribute names were renamed/reorganized.
- Selectors became invalid: Your XPath/CSS selectors no longer match the new DOM.
- Content moved: Data may now be in a different section, loaded in modals, tabs, or nested containers.
- JavaScript rendering changed: The site may now load data asynchronously, so static HTML fetches no longer contain the content.
- API endpoints changed: If your scraper depended on hidden JSON/XHR calls, those endpoints or payloads may have changed.
- Anti-bot protections increased: The redesign may have introduced Cloudflare, bot checks, captcha, rate limits, or header validation.
- Pagination/infinite scroll changed: Old “next page” links may be replaced by dynamic loading.
- Text/locale changes: Labels or formatting might differ, breaking regex or parsing logic.
- Authentication/session flow changed: Login, cookies, or token handling may no longer work.
How to diagnose quickly:
- Compare the old and new page source.
- Inspect the DOM after JavaScript loads in browser dev tools.
- Check whether your scraper is using stale selectors.
- Look for network requests that now carry the data.
- Test whether the issue is parsing vs fetching.
If you want, I can help you debug it step by step if you paste:
- the old selector/snippet,
- the new HTML (or a screenshot of the DOM),
- and the language/framework you’re using.
Brands