Why we killed the SEOMAX Chrome extension

We're removing the SEOMAX Chrome extension from the 1.4 release.

The extension shipped in SEOMAX 1.0 as a quick way to inspect a page's SEO signals without leaving the browser tab: meta tags, heading outline, structured data validation, a link-health overlay, and a one-click export into a SEOMAX project. For the first six months it was the most-clicked item in our own internal navigation. It turned out to be the most expensive thing we maintain.

Why it existed

The pitch was simple. Indie SEO operators switch between the SEOMAX dashboard and the live page they are researching twenty or thirty times a day. A browser extension reads the page directly, skips the round-trip through a fetch-render cycle, and lets you tag something into a project while looking at it. We used it ourselves daily, which is usually a good sign.

Why it's going away

The real reason is the permissions treadmill. Chrome's Manifest V3 tightened the set of host permissions we could request, and the ones we still needed (read every page the user visits, persist a per-site state) put the extension in the "sensitive" review queue at the Chrome Web Store. Every minor update since January has taken between five and eleven days to re-approve. The extension did not justify two months of review-queue latency across the year.

The second reason is narrower. Bookmarklets cover 80 percent of the use cases, and the SEOMAX dashboard already accepts a paste of raw HTML for the other 20 percent. The extension was not doing anything our own tooling could not do in a simpler way.

The third reason we are naming honestly. We wrote the extension in plain TypeScript without a framework. That was the right call for 2024, but it aged badly once Manifest V3's service-worker lifecycle started requiring event listeners that survive browser restarts. Rewriting it for 2026 meant adopting WXT or Plasmo, which is a stack we do not otherwise use. We did not want to add a framework to the studio's mental load for one product that has a workaround.

What we tried before dropping it

• We migrated from Manifest V2 to V3 in April 2025. The lifecycle rewrite took 1,100 lines of code.
• We rewrote the structured-data validator twice, once to avoid the new URL() constructor that broke on chrome-extension:// origins, and once to handle schema.org vocabulary updates.
• We wrote our own background message bus to work around the service-worker sleep-wake cycle. It worked. It was also 400 lines of code for functionality the browser used to give us for free.
• We talked to three other SEO indie studios about sharing a permissions-light fork. Nobody wanted to maintain it either.

What changes for users

If you were using the SEOMAX Chrome extension to tag pages into a project, the dashboard now has a "paste URL" input that does the same fetch-and-extract pass. Paste a URL, same output, no browser permission dance. The structured-data validator moved to the dashboard at /tools/schema-check. The link-health overlay is gone with no direct replacement.

The extension will not get a removal notice in the Chrome Web Store. We are leaving the 1.3 build listed for anyone who still relies on it, flagged as unmaintained. 1.4 of the dashboard ships on 2026-05-10 with the new paste input.