Acentics
Log inSign up

Documentation

What every part of Acentics does and how to use it — written against what's actually built, not what's planned. See what's not built yet for the honest list of what's still on the roadmap.

Overview

Acentics crawls your site, finds SEO problems, and — this is the part most tools don't do — can actually fix a lot of them directly in the HTML your server sends, without you editing code. That last part only works once you've installed one of the edge rewrite methods on a site; everything else (crawling, the meta editor, broken links, redirects) works as soon as a site is verified.

The core loop is: add a site → verify it → crawl it → fix what the crawl finds → install edge rewrite so the fixes actually reach visitors and crawlers. The "Get set up" checklist on the Overview page tracks exactly these steps.

Sites

A site is a domain you want Acentics to track. Add one from the Sites page or the site switcher in the header.

  1. 1Click "Add a site" and enter the domain (no https://, no www — just the bare domain).
  2. 2Acentics gives you a DNS TXT record to add (name @, value acentics-verify=...). This proves you actually own the domain before Acentics will crawl it or let you install anything on it.
  3. 3Add that record with your DNS provider, then click "Check verification." DNS changes can take a few minutes to propagate — if it fails right away, wait a bit and try again.
  4. 4Once verified, you can crawl the site, edit its meta tags, and set up edge rewrite. Removing a site deletes it — you'd need to re-verify from scratch if you add it again.

SEO / AEO visibility (edge rewrite)

This is the feature that makes Acentics different from a report-only SEO tool. Title/meta overrides, canonical tags, and redirects only exist in Acentics's database until something actually rewrites your site's real HTML on the way out to visitors — that something is an edge rewrite install. Without one, everything below still works as a dashboard, it just never reaches a real visitor or crawler.

From a verified site's row on the Sites page, open "Set up edge rewrite" and pick whichever matches how the site is actually built and hosted:

  • Cloudflare Worker — best if the site already runs through Cloudflare, or you don't mind moving its DNS there. Free, works regardless of the origin server.
  • PHP — for plain HTML/PHP sites on ordinary shared hosting. A script gets included on every page via auto_prepend_file.
  • Node.js — middleware for a site running its own Express (or similar) server.
  • Next.js — feeds overrides into Next's own generateMetadata(), plus a small middleware file for redirects.
  • WordPress — a real installable plugin, works underneath any theme.

After installing, click "Verify setup" — Acentics requests the live page and checks for a marker response header the install sets on every request. If it says not detected, double-check the install is actually active and that no host-level or plugin cache is serving an old copy of the page.

Bing and AI answer engines (GPTBot, ClaudeBot, PerplexityBot) never execute JavaScript — they only ever see the raw HTML your server sends. That's exactly what edge rewrite changes; a client-side script tag can't reach them no matter how it's built.

Crawling

A crawl starts at the homepage and follows same-domain links breadth-first, plus anything listed in sitemap.xml — so a page only reachable from a sitemap (not linked anywhere) still gets found. A single crawl covers up to 200 pages.

For every page it successfully fetches, the crawl checks:

  • Missing title or a title over 60 characters (likely to get truncated in search results)
  • Missing meta description or one over 160 characters
  • Broken page — a non-2xx response

It also runs broken-link checking, canonical duplicate detection, and redirect suggestions as part of the same pass — see those sections below.

On the crawl detail page you can search pages by title/URL, filter to only pages with issues, and set a recurring schedule (daily, every 3 days, weekly, monthly, quarterly, or every 6 months) with an optional email report sent after each run.

Meta Editor

Pick a site, then a crawled page, to set overrides for that exact page:

  • Title and meta description
  • Favicon URL
  • Canonical URL — usually set automatically (see Redirects section), but you can override it here
  • Any number of custom meta tags (e.g. og:title, twitter:card) by name/property + content

Saving here only changes what's stored in Acentics. It reaches the live page through whichever edge rewrite method is installed on that site — with nothing installed, an override sits saved but invisible to real visitors.

Every link found during a crawl — internal or external — gets checked. This page groups the ones that failed by site, and shows exactly which page(s) link to each broken URL and the anchor text used, so you know where to go fix it.

Broken links to a page that used to exist on your own site are exactly what feeds the Redirects suggestions below.

Redirects

After a crawl, Acentics compares every same-domain broken link against every page that did crawl successfully, using word-overlap similarity between the two paths. A close enough match shows up here as a suggested redirect with a match percentage — Approve to activate it, or Dismiss if it's wrong. You can also add a redirect manually.

Canonical URLs work similarly but don't need approval: when a crawl finds two URLs that are really the same page (a tracking parameter, or a trailing slash), it automatically points the non-preferred one at the preferred one — you can override the choice from the Meta Editor if it picks wrong.

Active redirects only take effect on the live site through whichever edge rewrite method is installed — the same as everything else on this list. Installed edge rewrite also rewrites any internal <a href> on your own pages that still points at the old path, healing links over time (not on the Next.js method — see its note in the edge rewrite setup panel).

Keywords

A list of keywords you're targeting, each against a site and optionally a specific page you want it to rank for, plus free-text notes.

This is a watchlist, not automated rank tracking — Acentics doesn't currently check where a keyword actually ranks in search results.

Profile & security

From the account menu (top right) → Profile, you can update your name and contact number, and see your workspace name and role. Email isn't editable yet — changing it safely needs a verification step that doesn't exist.

The same page has a change-password form — it requires your current password before setting a new one. Two-factor authentication and Google/Microsoft sign-in are visible in the account menu and login page but aren't wired up yet (see the roadmap).

Team & roles

Owners and admins can invite people to the workspace from the Team page. Add one or more emails, pick a role, and — for anyone other than Admin — choose which features they should land with access to; Acentics emails each of them an accept link that expires in 7 days. If SMTP isn't configured or a send fails, that invite is still created and the results screen shows a link you can copy and send yourself instead.

Four roles exist, each with strictly more access than the one below it:

  • Owner — full access, plus the only role that can't be changed or removed. Assigned once, to whoever signs up and creates the workspace.
  • Admin — full access, including inviting people, changing roles, and removing members.
  • Editor — can create, edit, and delete everything else (sites, crawls, redirects, meta overrides, keywords) but can't manage the team.
  • Viewer — read-only everywhere. Can see sites, crawl results, redirects, and keywords, but every action that changes something is blocked.

Only owners and admins can see or manage pending invites and change someone's role. Nobody can promote a member to owner or change/remove the owner's own role — ownership transfer isn't supported yet.

On top of role, an owner or admin can hide specific feature areas from an editor or viewer — Crawling, Meta Editor, Broken Links, Redirects, and Keywords each have their own switch, set either while sending the invite or afterward via the sliders icon next to a member. Turning one off removes it from that member's sidebar and search results and blocks the underlying pages entirely, even if they hit the URL directly. Everything is on by default; this is purely for narrowing someone down (e.g. a contractor who should only ever touch Broken Links).

Ctrl + K (or the search box in the header) opens a command palette that jumps straight to any of your sites, or to any page in the app — Overview, Sites, Crawling, Redirects, and everything else in the sidebar.

What's not built yet

These are visible somewhere in the app but genuinely aren't functional yet — listed here so it's clear rather than something you have to discover by clicking:

  • AEO/GEO citation tracking, Content, and Social — each shows a "not built yet" page
  • Reports & Alerts, and the rest of Settings (workspace name, integrations)
  • Ownership transfer — the owner role is fixed to whoever signed up
  • Two-factor authentication
  • "Continue with Google" / "Continue with Microsoft" on login — the buttons say so if you click them
  • Automated rank tracking behind Keywords (see above)