Guide 11 of 12
Instant Data Scraper Not Working? How to Fix It
Fix Instant Data Scraper problems: no data found, wrong table, Next button not working, blocked pages, JavaScript sites, broken exports and extension errors.

Whether you use the Instant Data Scraper browser extension or the online tool on instantdatascraper.net, sooner or later a page won't extract the way you expect. The good news: almost every problem has a small number of causes, and most can be fixed in a minute.
This troubleshooting guide is organised by symptom. Find what you're seeing, read the cause, and apply the fix. Sections cover both the online tool and the Chrome extension.
Quick checklist
- Does the page open in your browser without logging in?
- Is the data visible on the page (not inside an image or PDF)?
- Is the URL complete, including
https://? - Did you wait for the page to fully load (extension) or the progress bar to finish (online tool)?
- Have you tried another dataset or table?
"No structured data was found"
Cause 1: The content is loaded by JavaScript
Press Ctrl+U to view the page source and search for a value you can see on screen. If it isn't there, the page builds its content with JavaScript.
Fix: use JavaScript page mode in the online tool (where available), or the browser extension which reads the rendered page.
Cause 2: No repeating structure
Pages with free-form text don't contain table-like data.
Fix: use CSS selector mode to target specific elements, or choose a listing page instead.
Cause 3: Content is inside an iframe
Some widgets load another page inside a frame.
Fix: right-click the widget, choose Inspect, find the iframe's src URL and extract that URL directly.
The wrong table or block is extracted
- Online tool: click through the dataset tabs above the preview.
- Extension: click Try another table until the right block is highlighted.
- Still wrong? Use HTML table mode for tables, or CSS selector mode with the exact row selector.
Too many or messy columns
- Untick unnecessary columns before exporting.
- Values joined with " | " came from one element with several text parts — split them in Excel.
- Shifted values happen when some items lack a field — define named fields in CSS selector mode.
Access and network errors (online tool)
| Message | Meaning | What to do |
|---|---|---|
| Refused access (HTTP 401/403) | Login required or bots blocked | The tool won't bypass this. Use an official API or ask the owner. |
| Page not found (HTTP 404) | Wrong or outdated URL | Open the page again and copy the current URL. |
| Rate-limiting (HTTP 429) | Too many requests to that site | Wait and try later with fewer pages. |
| Took too long (timeout) | Slow or overloaded site | Retry later or use a lighter page. |
| Larger than the size limit | Huge page | Use a category page instead of "view all". |
| Disallowed by robots.txt | Site asked bots not to visit | Respect it; look for an allowed page or API. |
| Not a web page | URL is a PDF, image or download | Use a tool designed for that file type. |
| Private/local address blocked | Security protection | Only public websites can be extracted. |
| Domain could not be found | Typo or domain doesn't exist | Check the spelling. |
| Quota or too many requests | Plan or guest limit reached | Wait for the reset, sign in or upgrade. |
Pagination problems
Only the first page is collected
Check that Support pagination is ticked (online tool) or that the Next button was located (extension).
It stops after a few pages
- The Next link changes on later pages — provide a more general selector such as
a[rel="next"]. - The page limit was reached — increase it within your plan.
- The site started blocking requests — stop and try later with fewer pages.
Duplicate rows
Featured items repeat on each page; remove duplicates by URL in Excel.
Export problems
- Strange characters in CSV — import as UTF-8 or use the Excel export.
- Everything in one column — your region uses semicolons; import with Data → From Text/CSV.
- Download doesn't start — allow downloads/pop-ups for the site in your browser.
- Numbers stored as text — they contain symbols; convert with VALUE/SUBSTITUTE.
Chrome extension–specific problems
The icon does nothing
Reload the page and click again. Extensions cannot run on browser pages such as chrome:// or the Chrome Web Store.
The extension disappeared or stopped updating
Extensions can be disabled after policy changes or ownership changes. Check chrome://extensions, the store listing, and consider an alternative — see Best Instant Data Scraper Alternatives.
Blocked by your organisation
Managed work browsers often block extensions. Use the online tool instead — nothing to install.
Crawl skips data
Increase the minimum and maximum delay so each page loads completely.
Online tool–specific problems
- "Backend not reachable" — check your connection and refresh. On a self-hosted copy, make sure PHP and MySQL are running.
- "Session token missing or expired" — refresh the page.
- "JavaScript rendering is not enabled" — this installation doesn't have the renderer; use Automatic mode or another page.
Deep dive: JavaScript-heavy websites
Single-page applications (built with React, Vue, Angular and similar frameworks) are the most common reason for "nothing found". How to recognise them:
- The page source contains an empty container such as
<div id="root"></div>or<div id="__next">. - Content appears a moment after the page loads, often with a loading spinner.
- Disabling JavaScript in your browser makes the content disappear.
Options, from simplest to most involved:
- Use JavaScript page mode in the online tool (where enabled).
- Look for a server-rendered version — "basic HTML", AMP pages, print views or RSS feeds.
- Check whether the site publishes an official API or downloadable dataset.
Text and encoding problems
- Accented letters look broken — the file was opened with the wrong encoding; use the Excel export or import the CSV as UTF-8.
- Extra spaces or line breaks — clean with
=TRIM(CLEAN(A2)). - Text joined without spaces — the page placed words in separate elements without spacing; use CSS selector mode to extract each element as its own field.
- Hidden text included — some pages contain screen-reader text; untick that column or refine your selector.
Why websites block scrapers — and what that means for you
Websites block automated requests to protect server capacity, prevent data resale or enforce their terms. Signs you've been blocked include 403 or 429 responses, CAPTCHAs, or pages that return a short "access denied" message.
Instant Data Scraper treats these as a clear "no": it never rotates IP addresses, fakes browsers or solves CAPTCHAs. The right next steps are:
- Reduce the number of pages and try again later.
- Check the site's terms and robots.txt.
- Look for an official API, data export or partnership.
- Contact the website owner and ask for permission or a data feed.
How to report a problem effectively
If you believe the tool is wrong, include these details when you contact us:
- The exact URL you extracted.
- The mode and options you used (pagination, selectors).
- The approximate time of the job and the error message.
- What you expected to see (e.g. "24 product rows with price").
- A screenshot of the page area you wanted to extract.
Preventing problems in future
- Save working selectors and settings in a notes file per website.
- Use meaningful selectors (classes like
.price,itempropattributes) rather than generated ones. - Re-test after a website redesign.
- Keep extractions small and regular rather than huge and occasional.
Troubleshooting decision tree
- Did the job fail with an error message? Read it and use the error table above.
- Did it finish with no data? Check view-source. Data missing → JavaScript page mode. Data present → CSS selector mode.
- Did it return the wrong data? Switch dataset tabs, then try Table mode or CSS selector mode.
- Is only part of the data there? Enable pagination, or check the page and row limits of your plan.
- Is the export the problem? Use the Excel export, or import CSV as UTF-8.
Following these steps in order usually tells you what is wrong within a couple of minutes.
Why a working setup can suddenly break
Websites are updated constantly. A redesign can rename CSS classes, move the pagination links, switch a table to a card layout or start loading content with JavaScript. When that happens, a selector or setting that worked last month may return nothing today. This is normal and not a fault in the tool — it simply reflects that the page is now built differently.
The fastest way to recover is to repeat the basic checks: open the page, look at the structure with Inspect, run Automatic mode to see what the tool detects now, and update your selectors to the new class names. Choosing stable selectors in the first place — meaningful class names, schema.org itemprop attributes and data attributes — reduces how often this happens.
Still stuck?
If none of the fixes above work, the page may simply not be suitable for automated extraction — for example because the data is only in images, behind a login or protected by bot detection. In that case the best options are an official API or dataset, a direct request to the website owner, or careful manual collection of the few values you actually need.
Key takeaways
- Read the exact error message first — it usually tells you the fix.
- No data usually means JavaScript content or no repeating structure.
- Wrong data is fixed with dataset tabs, Table mode or CSS selectors.
- Access blocks, CAPTCHAs and robots.txt rules should be respected, not bypassed.
- Export problems are almost always encoding or delimiter settings.
Conclusion
Most scraping problems come down to a handful of causes: JavaScript-built pages, the wrong dataset, missing pagination settings, access restrictions or export encoding. Read the error message, check the page source, try another dataset or mode, and adjust selectors when a website changes. When a site blocks automated access, respect that decision and look for an official data source. With these steps, you can resolve nearly every issue quickly and keep your extractions reliable.
Step-by-step instructions
Read the exact message
Every failed job in the online tool shows a specific reason.
Open the URL in your browser
Confirm it's public and the data is visible.
Check view-source
If the data isn't in the source, use JavaScript page mode.
Try another dataset or mode
Switch tabs, then Table, Lists or CSS selector mode.
Retry later for network errors
Timeouts and 5xx errors are often temporary — press Retry.
Contact support
Send the URL, mode and time via the Contact Us page.
Example
A user sees "No structured data was found" on a property listing site. View-source shows <div id="root"></div> and no listings. Switching to JavaScript page mode returns 30 rows with address, price and link.
Best practices
- Start simple: one page, Automatic mode.
- Treat 403, 429 and robots.txt blocks as a 'no'.
- Use semantic selectors that survive redesigns.
- Keep a note of the settings that worked for each site.
- Use the online tool when extensions are blocked.
Open the Instant Data Scraper tool and extract your first dataset in seconds.
Frequently asked questions
Your browser may be logged in, run JavaScript or be treated differently by bot protection. The online tool only sees what a public, honest request receives.
Yes — each attempt is a new extraction job.
No. Instant Data Scraper never bypasses CAPTCHAs, logins, paywalls or anti-bot systems.
Signed-in users can open their extraction history on the Account page.
The website probably changed its layout or started loading content with JavaScript. Re-run Automatic mode and update your selectors.
Yes. Send the URL, the mode you used and the error message through the Contact Us page and we'll take a look.