Connect your website
“We couldn’t find the install code”: fixes
What to check when FactHound can’t find your code on your homepage. The most common causes come first.
How the check works
When you select Check for the install code, FactHound opens your homepage and reads its code, the way AI tools do. It doesn’t run JavaScript. If your code isn’t there, you see: “We couldn’t find the install code on your homepage. Check that it is in the header and that the change is published.”
Fix one thing at a time, then select Check for the install code again.
You didn’t save or publish
Most website builders keep your change as a draft until you save or publish it.
- Squarespace: select Save in Code Injection.
- Wix: select Apply in Custom Code.
- Webflow: save your changes in Custom code, then publish your site to your own domain.
- Other websites: save the template, then publish or upload the change.
Some builders take a minute or two to update your live site. Wait, then check again.
Your plan doesn’t allow custom code
Some website builders add custom code to your live site only on paid plans:
- Wix: a published site with a connected domain, which needs a Premium plan.
- Squarespace: a Core, Plus or Advanced plan.
- Webflow: a paid site plan.
FactHound can’t work around this. Upgrade your builder plan, or ask your builder’s support whether your plan allows custom code.
The code is in the footer, or on one page only
The code belongs in the header code: Header in Squarespace Code Injection, Head in Wix Custom Code, Head code in Webflow. If you pasted it into a Footer box, move it to the header.
FactHound only looks at your homepage. If you added the code in the settings of a single page, and that page isn’t your homepage, we can’t see it. Add it in the settings for the whole site instead. On Wix, apply it to All pages.
Only part of the code was copied
Use the copy button next to the code in the Install code card. When you select code by hand, it’s easy to miss part of it.
The code is added by a script
If a tag manager or another script adds the code, FactHound can’t see it, and neither can AI tools. Paste the code straight into your header code.
The code is on a different address
FactHound checks the address you added, for example yourbusiness.com. If the code is on another website, or only on a test address such as a webflow.io address, publish it to the address you added.
FactHound can’t open your homepage
After the check, you might see a different message:
- “Your homepage could not be reached. We’ll try again.” Your site may be offline, protected by a password, or not published yet. Make it public, then check again.
- “Your site’s robots.txt file blocks FactHound from reading it.” Ask the person who looks after your website to allow FactHound.
- “Your homepage redirects to another website.” Your address sends visitors to a different website. Add the website where visitors end up, or remove the redirect.
The check button is greyed out
Your FactHound role doesn’t let you manage connections. Ask a workspace admin to run the check or to change your role.
Need more help?
Email hello@facthound.co with your website address and what you see on the screen. We’ll help you finish.