# Getting the statement onto your website

Link, embed snippet, server-side retrieval or WordPress plugin – which way fits and how quickly a new version appears with each of them.

**In short**

- The simplest way is a link to the statement’s public address – in the footer of every page.
- If the text should appear on your own page, use the embed snippet, server-side embedding or the WordPress plugin.
- Every way except “use it yourself” only shows a published statement and follows each new version automatically.

Once published, your statement has a permanent public address. How it gets from there onto your website is up to you. One way is enough. What matters is that visitors can reach the statement from every page – usually through an “Accessibility” link in the footer.

## The ways compared

| Way | Requires | New version appears | Without JavaScript |
| --- | --- | --- | --- |
| Link to the public address | publication, from the Starter plan | immediately | yes |
| Embed snippet | from the Starter plan | within a few minutes | the link stays |
| Server-side embedding | from the Starter plan, your own server code | depends on your cache | yes |
| WordPress plugin | publication, from the Starter plan | after up to 60 minutes, plus page cache | yes |
| Use it yourself | none, in every plan | never on its own | yes |

## Link to the public address

After publishing, the address is shown in the website’s “Overview” tab, in the “Statement” section. The publishing page also offers a “Ready-made link for your footer”.

The public page is built to be accessible and contains the form visitors use to report barriers, the PDF and all earlier versions. It stays online even when your subscription ends – a linked statement must not lead nowhere.

## Embed snippet or server-side embedding

For systems without a plugin: TYPO3, Drupal, Webflow, a custom frontend. The text then sits on your own domain and follows every new version. Setup, allowed domains and what happens after a subscription ends: [Embedding the statement without a plugin](https://barrierepruefung.de/en/help/embedding).

## WordPress plugin

The plugin places the text on a page with a shortcode or block and starts scans straight from WordPress. It verifies the domain without DNS access. [Set up the plugin](https://barrierepruefung.de/en/help/wordpress-setup) · [Show the statement](https://barrierepruefung.de/en/help/wordpress-shortcode)

## Use it yourself

You download the draft as Markdown and copy it into your system – possible in every plan. The reporting channel for barriers, the date of the last review and the archive of earlier versions are then your responsibility, and a new scan does not change your text. [Using the draft yourself](https://barrierepruefung.de/en/help/using-the-draft-yourself)

## Which way fits?

- **Your website runs on WordPress:** the plugin.
- **Another system, and you can add server code:** server-side embedding – the text is then part of the page even without JavaScript.
- **You can only paste HTML:** the snippet.
- **You don’t want to build anything in:** a link in the footer.

---

Last checked against the product: 2026-09-13 · https://barrierepruefung.de/en/help/getting-the-statement-on-your-site