Auto-updating cookie policy and cookie table for WordPress
Generate a cookie policy page from your cookie scan, add the Cookie table block or shortcode, and keep the cookie list up to date automatically.
On this page
A cookie policy tells visitors which cookies your site uses, why, for how long, and how to change their mind. Omea Consent writes the policy for you from your latest scan, and keeps the cookie list in it up to date.
Generate a cookie policy
- Scan your site Run a cookie scan so the cookie table has something to show.
- Review the cookies Under Omea Consent › Cookies check each cookie’s category, purpose, provider and duration. Turn Show off for anything you don’t want listed, then click Save changes.
- Generate the policy Go to Omea Consent › Settings › Policies and click Generate from scan in the Cookie policy card. If no cookie policy page is set, a draft page called Cookie Policy is created.
- Review and publish Open the draft, adjust the wording to your site and publish it.
- Link it Choose your privacy policy page in the Privacy policy card, and link the cookie policy from your footer.
What the generated policy contains
The draft is written in your site’s language and includes:
- What are cookies? – a short explanation.
- How we use cookies – your four categories with the descriptions from Settings › Categories.
- Your choices – how to change or withdraw consent, with a link that opens the cookie settings.
- Cookies we use – the live cookie table.
- More information – a link to your privacy policy page, if you’ve chosen one.
In advanced Consent Mode it also explains Google’s cookieless measurements before consent.
If a cookie policy page is already set, Generate from scan adds the cookie table block to it instead – unless the page already has the block or the shortcode. Your own text is left alone.
The cookie table
The table lists every cookie from your latest scan, grouped by category, with Cookie, Purpose, Provider and Duration, and ends with Last updated (the scan date). It uses your theme’s font and colours, and stacks into cards on phones.
Add it anywhere in two ways:
- Block editor: add the Cookie table block (in the Widgets category).
- Shortcode:
[omea_consent_cookie_table]– works in classic editors and page builders.
Because the table is dynamic, every new scan updates it on your published page automatically. Omea’s own consent cookie is always listed.
Edit cookie details
Change a cookie’s category, purpose, provider or duration under Omea Consent › Cookies. What you set there is shown in the cookie table and the preferences window. Use the Show switch to hide a cookie from the public table.
Keep the policy current
The table updates itself with each scan. With Omea Consent Pro, a cloud scan runs every month and emails you when something new appears – so the policy stays accurate without you remembering to check.