<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Dan Pan</title>
    <description>The latest articles on DEV Community by Dan Pan (@gingermanymph).</description>
    <link>https://dev.to/gingermanymph</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3963246%2Fc4dc0c6f-9326-421d-9e1e-4d82eca71e79.jpeg</url>
      <title>DEV Community: Dan Pan</title>
      <link>https://dev.to/gingermanymph</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/gingermanymph"/>
    <language>en</language>
    <item>
      <title>I built a browser checklist tool for SEO audits and QA</title>
      <dc:creator>Dan Pan</dc:creator>
      <pubDate>Tue, 02 Jun 2026 05:27:03 +0000</pubDate>
      <link>https://dev.to/gingermanymph/i-built-a-browser-checklist-tool-for-seo-audits-and-qa-413i</link>
      <guid>https://dev.to/gingermanymph/i-built-a-browser-checklist-tool-for-seo-audits-and-qa-413i</guid>
      <description>&lt;p&gt;Every time I do a website audit I run into the same problem. The checklist is open in one tab, the page I'm auditing is in another, and every time I need to mark something off I lose my place. Multiply that across 15 pages and it turns into a lot of unnecessary context switching.&lt;/p&gt;

&lt;p&gt;I looked for a browser extension that would keep a checklist open next to the page I'm working on — something that lives in the side panel, not in a separate tab or window. I didn't find anything that fit, so I built it.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it does
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://checkrun.co/" rel="noopener noreferrer"&gt;CheckRun&lt;/a&gt; is a Chrome extension that runs in the browser side panel. The core model is simple: build a template once, run it against any page.&lt;/p&gt;

&lt;p&gt;When you open a run, the extension captures the URL and page title automatically. You go through each item marking it Pass, Fail, or N/A, leave comments where needed, and save the run when done. Every completed run is stored in history with its date, URL, and full item-level results.&lt;/p&gt;

&lt;p&gt;The side panel stays open while you navigate — so you can check an item, click to a different part of the page, come back, and your checklist is exactly where you left it.&lt;/p&gt;

&lt;h2&gt;
  
  
  The features that actually matter for audits
&lt;/h2&gt;

&lt;p&gt;A few things made this useful beyond just a basic checklist:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Per-template statistics.&lt;/strong&gt; After running the same audit template a few times, you get a pass rate trend and a breakdown of which items fail most often. Useful for identifying where a site consistently has problems — or where your audit process has gaps.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Run history tied to URLs.&lt;/strong&gt; Every run is stored with its URL. If a client asks "did we check this page last month?" — you have the answer, with item-level results.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Template sharing.&lt;/strong&gt; You can export a template as JSON, a short token, or a deep-link URL that opens it directly in the extension. Useful for sharing a standard audit process across a team.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Google Sheets export.&lt;/strong&gt; Results push to a spreadsheet with one click — one tab per run. If you're doing audits for clients and need to hand off a structured report, this saves a lot of manual work.&lt;/p&gt;

&lt;h2&gt;
  
  
  The audit template
&lt;/h2&gt;

&lt;p&gt;There's a ready-made &lt;a href="https://checkrun.co/templates/website-audit-checklist/" rel="noopener noreferrer"&gt;website audit checklist&lt;/a&gt; template that covers the standard on-page and technical checks — title tags, meta descriptions, heading structure, canonical tags, image alt attributes, page speed signals, mobile rendering, structured data, internal linking. It imports into the extension in one click.&lt;/p&gt;

&lt;p&gt;You can customize it from there — add sections for your specific process, remove items that don't apply, reorder as needed.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I learned building it
&lt;/h2&gt;

&lt;p&gt;The hardest part wasn't the checklist logic — it was working within Chrome's MV3 restrictions. Service workers instead of background pages, stricter CSP, the side panel API which is still relatively new. A few things that caught me:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The side panel doesn't persist across browser restarts by default — you have to handle state restoration explicitly&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;chrome.storage.local&lt;/code&gt; has a 10MB limit per item that's easy to hit if you're storing large run histories — had to add pagination&lt;/li&gt;
&lt;li&gt;The side panel can't be opened programmatically without a user gesture, which changes how you handle the first-run experience&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Nothing insurmountable, but worth knowing if you're building something similar.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;CheckRun is free, no account required. Everything is stored locally — no server, no telemetry.&lt;/p&gt;

&lt;p&gt;Chrome Web Store: &lt;a href="https://chromewebstore.google.com/detail/checkrun/dakcmldkpfcfbckjacbpffefedgaeece" rel="noopener noreferrer"&gt;CheckRun&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Would be curious to hear how others handle repeatable audit workflows in the browser — what tools or approaches have worked for you.&lt;/p&gt;

</description>
      <category>showdev</category>
      <category>productivity</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
