Check if your site has a privacy policy

SiteCurl looks for a privacy page at paths like /privacy, /privacy-policy, and /legal/privacy. It also checks your footer for links that say 'privacy.' If a page is found, SiteCurl checks it returns a 200 status code.

The check does not judge the text of the page. It just confirms that a privacy page exists and can be reached from your site.

This is one of a few trust signal checks under the tech health part.

Privacy pages are one of those things nobody reads but all expect. If your site collects any data at all (contact forms, tracking tools, cookies, email signups), users and rules say you need a page that says what you collect and how you use it.

GDPR (EU), CCPA (California), PIPEDA (Canada), and dozens of other laws ask sites to share their data handling. The exact needs vary, but the base is the same: if you collect user data, you need a page that says so.

Google's ad tools (AdSense, Google Ads) need a privacy page to use the service. Apple's App Store needs one for any app with a web part. Stripe needs one for sites that take payments. Not having a privacy page can block you from using these tools.

Beyond rules, a privacy page is a trust signal. A site that openly says how it handles data looks more real than one that does not. Users may not read the full page, but they notice if the link exists.

A missing privacy page can put your firm at legal risk. GDPR fines can reach millions of euros. CCPA gives users in California the right to sue. The risk is real, and a privacy page is step one toward meeting these laws.

Users look for a privacy link, most of all before filling out forms or typing in payment data. A missing link at the bottom of a signup form raises doubts about how their data will be used.

Third-party tools need a privacy page too. Google Tracking, AdSense, Facebook Pixel, and Stripe all ask that your site has one. Not having it can lead to account bans or denied service.

Online stores that collect payment and shipping data need a privacy page for PCI rules and data laws. Buyers who do not see one may leave their cart.

SaaS tools that handle user accounts and data need a privacy page before taking signups. Large buyers check for one during vendor review. A missing page is a deal-breaker for many buying teams.

Any site using Google tracking, cookies, or contact forms collects user data and should have a privacy page. This includes blogs, folios, and info sites that seem too small to need one.

Step 1: Write a privacy page. Cover: what data you collect, how you use it, who you share it with, how long you keep it, and how users can reach you about their data. Use plain words, not legal talk.

Step 2: Link it from your footer. Put the link in the site footer on each page. Users expect it there. Also link it near any forms that collect user data.

Step 3: List your third-party tools. If you use Google tracking, list it. If you use a chat widget, list it. If you use cookies for any reason, say which ones and why. Each tool that collects data should be named on your page.

Step 4: Keep it fresh. When you add a new tracking tool, CRM link, or ad tool, update the page. An old page is better than none, but a current one is best.

Copying from a new site. A copied page may not match your real data use. It may cite tools you do not use or skip tools you do. Write one that fits your own data handling and tools.

Using a page maker and not reading what it wrote. Makers are a fine start, but read the output. Make sure each claim matches what your site does in practice. A page that says you do not collect data while you run Google tracking is wrong and could be a legal issue.

Linking to a page that returns a 404. This is worse than not linking at all. It tells users the page was there but got taken down. Check that the page loads after you add the link.

After creating your privacy policy, run another SiteCurl scan. The check should pass. Visit your site and scroll to the footer to confirm the link is visible and leads to a working page.

Click the privacy link from multiple pages to verify it works site-wide, not just from the home page.

A privacy page is expected by users, required by rules, and needed for most third-party tools. Create one that reflects your actual data handling, link it from your footer, and update it when your tools change. It guards your firm and builds user trust.