Collect WordPress website feedback on the rendered page so a client can show which heading, image, or form needs attention. Annot8 installs through a hosted script rather than a dedicated WordPress plugin. The setup depends on whether your site permits custom JavaScript; the review process depends on which pages and roles the client needs to test.
Check custom JavaScript access before choosing an installation method
First identify whether you run self-hosted WordPress or WordPress.com. Hosting restrictions, user permissions, and the available code-insertion tools differ. WordPress.com documents which code its plans support; check the current requirements rather than assuming that a Custom HTML block will execute a script. A Code block displays source text and is not a site-wide widget installation.
On a site you administer, use an existing, maintained site-wide script field or code-insertion plugin if one is available. Keep the installation out of individual posts. If your developer manages it in a theme, use an update-safe implementation and record where it lives so a theme change does not silently remove the review tool.
Configure the WordPress review host and add the generated snippet
- Create an Annot8 project for the website and add the exact domain used for the review.
- Create or check the staging environment for your staging hostname. Include the production hostname separately if it is in scope.
- Copy the complete snippet from Project → Settings → Installation, including the project key and backend URL.
- Add it once through your site-wide script mechanism, then publish or save that configuration.
- Clear the relevant WordPress or CDN cache and open the published page in a fresh browser session.
If the script loads but the launcher is absent, check the hostname and environment rules before reinstalling. On production hosts, Annot8’s Show widget in production setting controls the whole panel. A WordPress page cache can also serve the HTML from before the snippet was added. Check the response for the actual review URL, not only the saved admin setting.
Review WordPress page families and visitor roles
Choose representative templates: a homepage, an article, an archive, a landing page, and a form. A correction to a shared block or theme template can affect many pages; a comment on one post may be a content exception. Ask the reviewer to say which is intended. Include a long title and a page with realistic content so the review does not depend on an unusually tidy sample.
| Check | Review as | Record |
|---|---|---|
| Navigation and responsive layout | Signed-out visitor | Page, viewport, and selected element |
| Copy and reusable blocks | Client content owner | Exact replacement text and affected page family |
| Inquiry or signup form | Test visitor | Expected confirmation and actual delivery |
| Restricted content | Authorized test account | Role and permitted outcome without private data |
The WordPress admin bar changes the available viewport and can obscure a spacing issue. Recheck visual reports while signed out, then test authorized member views separately if they are part of the project. Annot8 guest links do not grant access to a password-protected website; give reviewers the site access they need through your normal process.
Keep revisions and approval tied to the release
Give each report one owner and one next action. Include exact replacement copy for factual corrections, the intended behavior for bugs, and a decision owner for new design directions. Annot8 can preserve the selected element, screenshot, and browser context. Paid plans add recordings and tracker delivery when a screenshot is insufficient.
After the change, clear the relevant cache and revisit the affected page family at the reported viewport. Verify form delivery separately from the success message. Record which release the client approved and which known issues remain. This turns a collection of WordPress comments into an acceptance record your team can use.
