Before writing a privacy page, list the services active on the site: AdSense or other advertising, analytics, embedded video, contact forms, email subscriptions, payment tools, and consent software. Use that inventory to make the page accurate. Google’s required-content article describes disclosures for advertising cookies, third-party vendors, personalized advertising, and opt-out information. The page should reflect your real setup, and legal requirements can vary by location; a template is not legal advice.
In WordPress, create a page with a clear title such as “Privacy Policy.” WordPress may provide a privacy-policy page setting under Settings → Privacy, but the exact interface depends on version and theme. Add the page to a visible footer or menu. Do not hide it behind a login. Preview it on mobile, click the link from several templates, and confirm the page returns successfully.
Example: If your site uses Google ads and an embedded YouTube video, make sure the policy does not describe advertising cookies but ignore the embedded service. If you remove a plugin, revisit the policy and remove outdated statements. Conversely, when you add a new tracking or marketing service, update the disclosure before relying on it.
After publishing, open the URL in a private browser and check that the text is readable, the links work, and the policy matches the live site. Keep a version date only when you actually review and revise the document.
Run SiteReadyScore to check public discoverability and link access for the privacy page. Then compare your content against Google’s current guidance and the site’s real configuration. The scan can confirm that a page exists; it cannot tell whether every disclosure is complete or legally sufficient.