When you see a formula parse error IMPORTXML message, it typically means your syntax is malformed, such as missing quotes around the XPath or an unescaped special character. The #ERROR! result, on the other hand, usually indicates the function ran but failed to retrieve or interpret the data, often due to blocked requests or invalid XPath queries. Fixing parse errors requires correcting your formula structure, while resolving #ERROR! means addressing the data source or query itself.
What exactly is a formula parse error in IMPORTXML?
A formula parse error occurs before Google Sheets even attempts to fetch data. The spreadsheet cannot interpret what you have written, so it refuses to execute the function. Common causes include:
- Missing quotation marks around the URL or XPath string
- Using straight quotes copied from a word processor instead of standard double quotes
- Forgetting to close a parenthesis
- Including unescaped characters like ampersands or angle brackets in your XPath
For example, this formula will fail with a parse error:
=IMPORTXML(https://example.com, //h1)
The correct version wraps both arguments in quotes:
=IMPORTXML("https://example.com", "//h1")
If you copy a URL from a browser that includes special characters, you may also encounter issues. Encode ampersands as & when necessary, or store the URL in a separate cell and reference it.
Why does IMPORTXML return #ERROR! instead of data?
When the formula syntax is valid but the function still fails, you will see #ERROR! with a tooltip like "Could not fetch URL" or "Resource at URL not found." This happens because:
- The website blocks automated requests (common with JavaScript-heavy sites)
- The server returns a non-200 HTTP status code
- Your XPath does not match any elements on the page
- Google's servers are temporarily rate limited by the target site
If you hover over the error, Sheets sometimes provides additional context. For deeper troubleshooting, see our guide on IMPORTXML could not fetch URL errors.
How do I fix IMPORTXML XPath errors?
XPath errors account for a large share of formula parse error IMPORTXML problems. Even when the formula itself is syntactically correct, a malformed XPath will return nothing or throw an error.
Start by testing your XPath in browser developer tools. In Chrome, open the console and run:
$x("//h1")
This returns all <h1> elements. If you get an empty array, your XPath does not match the page structure.
Common XPath mistakes:
- Using single slashes when you need double slashes (
//selects anywhere in the document,/requires the exact path) - Forgetting that XPath is case-sensitive
- Querying elements that load via JavaScript after the initial page render
If your XPath works in the browser but fails in Sheets, the page likely requires JavaScript execution. IMPORTXML only reads the raw HTML source, not the rendered DOM. For these sites, consider switching to a tool that processes pages server-side. Our comparison of IMPORTXML vs Enrich explains when each approach makes sense.
Does robots.txt block IMPORTXML?
Yes. Many websites include a robots.txt file that disallows automated scraping. Google Sheets respects these restrictions, so IMPORTXML will fail silently or return an error on blocked domains.
You cannot override this within Sheets. If you need data from a site that blocks automated access, you have two options:
- Contact the site owner and request API access
- Use a dedicated enrichment tool with proper rate limiting and fallback logic
We cover this scenario in detail in IMPORTXML blocked by robots.txt.
What does "Imported content is empty" mean?
This message appears when IMPORTXML successfully fetches the page but your XPath returns no matches. The formula did not encounter a parse error, and the URL was accessible. The problem is that the elements you are targeting do not exist in the raw HTML.
Reasons this happens:
- The content is loaded dynamically with JavaScript
- The page structure changed since you wrote the formula
- You are using an XPath that targets attributes or classes that vary between pages
For troubleshooting steps, see IMPORTXML imported content is empty.
Are there limits to how many IMPORTXML calls I can make?
Google Sheets imposes several constraints that affect IMPORTXML:
- Each spreadsheet can make a limited number of external requests
- Responses are cached for a period, so rapid updates will not refresh data immediately
- Large result sets can exceed cell limits
If you are scraping data at scale, these limits become a serious bottleneck. For a broader overview of constraints, read Google Sheets limits that stop big jobs.
When should I use an alternative to IMPORTXML?
IMPORTXML works well for simple, static pages where you control the source or know the structure will not change. It struggles with:
- Sites that block bots
- JavaScript-rendered content
- Pages requiring authentication
- High-volume scraping tasks
For enriching lead lists with company data, a purpose-built tool handles these edge cases more reliably. ReplyLabs' Enrich feature reads company web pages, extracts relevant information, and writes it directly to your spreadsheet. Unlike IMPORTXML, it processes pages server-side and includes fallback logic for common failure modes.
You can explore how this works in our guide on enriching URLs in Google Sheets. If you are building outbound campaigns, pairing enrichment with email verification helps reduce bounce rates before you export your list to a sequencer.
How do I debug a persistent IMPORTXML error?
Follow this checklist:
- Confirm your formula syntax is correct (quotes, parentheses, commas)
- Test the URL in a browser to ensure it loads
- Verify your XPath in browser developer tools
- Check if the site blocks automated requests
- Wait a few minutes and retry, in case of rate limiting
If the error persists after all checks, the site likely requires JavaScript rendering or blocks Google's IP ranges. At that point, IMPORTXML is not the right tool for the job.
Can I run AI prompts on scraped data?
Yes. Once you have data in your spreadsheet, whether from IMPORTXML or another source, you can process it with AI prompts. ReplyLabs lets you run AI prompts across entire columns, summarising page content, extracting specific details, or scoring leads based on firmographics.
This workflow is especially useful when scraping returns raw text that needs interpretation. Instead of writing complex XPath queries to isolate every field, you can pull the full text and let the prompt extract what you need.
How does ReplyLabs help with URL enrichment?
ReplyLabs Enrich reads company web pages and writes structured data back to your spreadsheet. It handles common failure modes, including JavaScript-rendered content, rate limiting, and blocked requests, that cause IMPORTXML to fail.
The add-on costs $0.005 per enrichment at the Starter tier, or $0.0025 at higher volumes. Because it runs server-side, you avoid the execution limits that affect native Sheets functions. For complex workflows, you can chain multiple enrichment steps or combine URL data with AI prompts in Google Sheets.
This approach is particularly valuable when preparing outbound lists. Rather than manually fixing formula parse error IMPORTXML issues row by row, you get consistent results across your entire dataset. The enriched data then feeds into your sequencer of choice, while ReplyLabs handles the preparation work.
Common questions
Why does my IMPORTXML formula work for some URLs but not others?
Each website has different server configurations. Some block automated requests, some require JavaScript, and some have varying page structures. A formula that works on one domain may fail on another due to these differences.
Can I use IMPORTXML to scrape LinkedIn or other social platforms?
No. Major platforms block automated scraping and require authentication. IMPORTXML cannot handle login flows or bypass these restrictions. For LinkedIn company data, consider enriching LinkedIn company pages through a dedicated tool.
How often does IMPORTXML refresh its data?
Google Sheets caches IMPORTXML results for up to one hour. You can force a refresh by adding a changing parameter to your URL or by using a helper cell with NOW(), though this increases the chance of hitting rate limits.
Is there a way to handle IMPORTXML errors gracefully in my spreadsheet?
Wrap your formula in IFERROR to display a fallback value when the function fails. For example: =IFERROR(IMPORTXML("https://example.com", "//h1"), "Data unavailable"). This prevents error messages from cluttering your sheet while you troubleshoot.