SEO Toolkit

Open the page, click the extension icon, and the popup analyzes what is currently rendered. Because it reads the live DOM through a content script, it sees content that a server-side crawler would miss on a JavaScript-rendered page. It also works on staging URLs, localhost, and pages behind a login, since nothing has to be publicly reachable for the analysis to run.

Open the SERP tab and it builds the snippet from the page's own title, meta description, and URL. The desktop view truncates at 60 and 160 characters, the mobile view at 78 and 120, and a live counter shows how far over or under you are. If the page has no meta description, the preview says so rather than inventing one.

Yes — the Links tab requests each unique URL, starting with a HEAD request and retrying with a ranged GET if that fails. One caveat worth knowing: cross-origin responses come back opaque, so the check confirms that a URL responded at all rather than reading its status code. Links that fail outright — dead hosts, refused connections, timeouts after 10 seconds — are the ones it flags and highlights on the page.

Not usefully. The tokenizer splits visible text on Latin letters, digits, and underscores and filters an English stop-word list, so CJK text does not produce countable tokens. The other five tabs — score, SERP, headings, links, meta — are language-independent, and the popup interface itself is available in English and Korean.

The manifest declares activeTab, storage, scripting, and webNavigation, plus host access to all sites. Host access and scripting exist because the content script has to be injectable into whatever page you are auditing, including one that was already open before you installed it. storage keeps popup state such as the last tab you used. webNavigation feeds the background worker, and what that worker does is worth stating plainly: it watches tab loads, and for a URL that matches its rule set it can navigate the tab to a different address and records an analytics event named nav_update carrying the page URL. Those rules are bundled inside the published extension rather than fetched from a server. That behavior is separate from the audit, which runs only when you open the popup.