How to Fix Missing Privacy Policy and Terms Links
This check warns when your page has no link to a privacy policy, no link to a terms page, or neither. By the end of this guide you will have published both pages at clear URLs, linked them from a sitewide footer, and confirmed the links appear in the page HTML.

Why it matters
Privacy and terms pages are a basic trust signal for visitors, payment providers, ad platforms and app stores. Google Ads, Merchant Center, Stripe and OAuth consent screens often require a reachable privacy policy and may reject an account that lacks one. GDPR, UK GDPR and US state laws such as CCPA/CPRA also expect a privacy notice that visitors can find easily.
Search quality raters and AI assistants look for this information when they judge whether a business is legitimate. The direct ranking effect is small, but a missing link can block ad approval, checkout setup and user trust.
What you need
Step-by-step fix
Check which pages already exist
Search your CMS pages list for any existing privacy, terms, legal or conditions pages. Many sites already have these pages, but they sit at vague URLs like /page-12 or /info and are not linked anywhere. If a page exists, update it and fix its URL rather than creating a duplicate.
Write or update the privacy policy
The policy must describe what you actually do. At minimum, cover:
- Who you are, with a contact email and postal address
- What data you collect: forms, cookies, analytics, orders
- Why you collect it and the legal basis (needed under GDPR)
- Third parties that receive the data, such as Google Analytics, Stripe or Mailchimp
- How long you keep data, and how users can access or delete it
- A 'Last updated' date
Write or update the terms page
Your terms of use or terms and conditions should cover:
- Acceptable use of the site
- Intellectual property
- Disclaimers and limitation of liability
- Governing law
- For e-commerce: payment, shipping, returns and refunds
Add a 'Last updated' date here too.
Use descriptive URLs for both pages
Set the page slugs so the URL itself contains the right words. Use privacy or privacy-policy for the privacy page. Use terms, terms-of-service, terms-and-conditions or legal for the terms page.
The audit identifies these pages by their link address, so a terms page at /tos or a privacy page at /datenschutz will not be recognised.
https://example.com/privacy-policy https://example.com/terms
Link both pages in the sitewide footer
Add the links to your footer template or footer menu so they appear on every page, including the homepage. Use plain <a href> links in the HTML. Do not rely on buttons, JavaScript click handlers, or links that only appear after a cookie banner loads.
<footer>
<nav aria-label="Legal">
<a href="/privacy-policy">Privacy Policy</a>
<a href="/terms">Terms of Service</a>
</nav>
<p>© 2026 Example Co</p>
</footer>Make sure the pages are indexable
Open both pages and check three things:
- There is no
noindexmeta tag - They return a 200 status
- They are not blocked in robots.txt
Legal pages do not need to rank, but they should be reachable by crawlers and verification bots used by ad and payment platforms.
curl -sI https://example.com/privacy-policy | head -1 curl -sI https://example.com/terms | head -1
Verify the links appear in the page HTML
Load your homepage and view the source with Ctrl+U (Cmd+Option+U on Mac). Search the source for 'privacy' and 'terms'. Both href values should be there.
If they only show up in DevTools Elements but not in the source, they are injected by JavaScript and may be missed. Re-run the audit afterwards.
curl -s https://example.com/ | grep -Eio 'href="[^"]*(privacy|terms|legal)[^"]*"'
Platform-specific notes
WordPress
Go to Settings > Privacy to create or select the privacy policy page. WordPress pre-fills a template you must edit. Set the slug in the page editor under Page > URL. Add both links via Appearance > Menus (classic themes) or Appearance > Editor > Patterns > Footer (block themes). Plugins like Complianz can generate the pages.
Shopify
Go to Settings > Policies to create the Privacy policy and Terms of service. Shopify serves them at /policies/privacy-policy and /policies/terms-of-service. Add them under Online Store > Navigation > Footer menu > Add menu item > Policies, and make sure your theme's footer section displays that menu.
Wix
Add a page from Pages & Menu > + Add Page > Policies (Privacy Policy, Terms & Conditions). Set the URL slug under the page's SEO basics settings. Then add the links to the footer, which is shared across all pages by default.
Webflow
Create static pages and set the slug in Page Settings. Add the links inside your Footer component (or Symbol) so they update sitewide, then publish to every domain, including the custom domain and not just webflow.io.
Next.js
Create app/privacy-policy/page.tsx and app/terms/page.tsx. Link them from the footer in the root layout.tsx using <Link href="/privacy-policy">. These render as real <a> tags in the server HTML. Avoid router.push buttons for these links.
Check that it worked
✅ How to verify
- Re-run the audit; the check should read 'Privacy and terms pages are linked.'
- View the homepage source and confirm href values containing 'privacy' and 'terms' (or 'legal'/'conditions') are present without JavaScript.
- Click both footer links on desktop and mobile and confirm each returns a 200 page with current content and a recent 'Last updated' date.
- Use Google Search Console URL Inspection on both legal URLs to confirm they are crawlable and not marked noindex.
⚠️ Common mistakes
- Using URLs that don't name the page, such as /tos, /p/123 or a non-English slug, so the link isn't recognised as a privacy or terms page.
- Loading the footer or legal links only through JavaScript or a cookie consent widget, so they are missing from the HTML.
- Copying another company's policy that lists tools, addresses or data practices you don't actually use.
- Hiding the footer on landing pages or checkout templates, which removes the legal links exactly where data is collected.
Is this still an issue on your site? Run a free audit — ZORO checks this and 294 other SEO, AI-visibility, accessibility and security signals, with fixes for your platform.
Check my site freeFAQ
Is a privacy policy legally required for a small website?
In most cases, yes. If you use analytics, cookies, contact forms, newsletters or take payments, laws such as GDPR, UK GDPR, CCPA/CPRA and Canada's PIPEDA require a privacy notice. Google Ads, Stripe and app stores also require one.
Do I need a terms and conditions page if I don't sell anything?
It is not usually a legal requirement, but terms of use protect your content and limit your liability. Many platforms, including OAuth app verification, ask for a terms URL as well.
Can the privacy policy and terms be on one page?
You can use a single /legal page with sections for each. Separate pages are clearer for users and are easier to supply to platforms that ask for distinct privacy and terms URLs.
Should privacy and terms pages be noindexed?
No. Keep them indexable. They rarely compete for rankings, and leaving them crawlable helps search engines and verification bots confirm your business is legitimate.
How to Fix Scannable Formatting: Headings, Lists and Tables
How to Fix Missing About and Contact Page Links
How to Create Comparison and Alternatives Pages for SEO
How to Fix Missing Trust Signals: Reviews, Badges & Guarantees
How to Add a Glossary and Definition Pages to Your Site
How to Fix an Unclear Value Proposition in Your Homepage H1