π What the Error Means
When you try to recrawl a page in Site Audit, you may see a message that says integer required. In plain language, the platform expected a whole number (such as 5 or 120) but received something else, like a blank value, text, or a decimal. This usually happens when the recrawl request is not passed to the system correctly.
This message does not mean there is a problem with your website, and it does not affect your existing audit results. It only means the recrawl request could not be processed.
π€ Why It Happens
The most common causes are:
- The audit page was left open for a long time, and the session or page data became outdated.
- The page you selected did not load fully, so the platform could not read its internal ID number.
- A numeric setting, such as a page limit, was left empty or contains letters, spaces, or decimals.
- A temporary glitch occurred while the request was being sent.
- A browser extension or cached data interfered with the request.
β Quick Fixes to Try First
Work through these steps in order. Most customers resolve the error within the first few.
- Refresh the page. Reload Site Audit so the latest data is loaded, then try the recrawl again.
- Re-select the page. Go back to the list of audited pages, choose the page again, and start the recrawl from there.
- Check any number fields. If you see a field for a page limit or similar setting, enter a whole number only. Do not use decimals, commas, letters, or leave it blank.
- Log out and back in. This refreshes your session and often clears request errors.
- Clear your browser cache. Then reload the platform and try again.
- Try another browser or a private window. This helps rule out extensions or stored data causing the problem.
π Alternative Ways to Recrawl
If the single-page recrawl still shows the error, you can try one of these options:
- Start a new full audit of your site instead of recrawling one page.
- Wait a few minutes and retry. If a crawl is already running, a new request may not be accepted until it finishes.
- Make sure the page is still live and reachable. Pages that are redirected, removed, or blocked can cause unexpected request problems.
π‘ Tips to Avoid the Error
- Avoid leaving Site Audit open for many hours before running a recrawl.
- Wait for the page list and results to fully load before clicking recrawl.
- Use whole numbers only in any numeric field.
- Keep your browser up to date and pause extensions that modify web pages, such as ad blockers or script blockers, if problems continue.
π What to Share If the Error Continues
If none of the steps above work, gather the following details so our team can help you faster:
- The URL of the page you tried to recrawl
- The project or site name
- The exact message you see on screen, or a screenshot
- The browser you are using
- The time the error occurred
π¬ Need More Help?
If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.