fix(core): file origin is null so use href to resolve relative links

Author: antlio

apps/cli/src/ui/action-menu.tsx

@@ -70,6 +70,7 @@ export const ActionMenu = ({
         setDone(true)
         setTimeout(() => {
           exit()
+          process.stdout.write("\n")
           if (result.overall_score < 50) process.exit(1)
         }, 50)
         break
@@ -90,7 +91,10 @@ export const ActionMenu = ({
         handleAction(option.value)
       } else if (char === "q" || key.escape) {
         setDone(true)
-        setTimeout(() => exit(), 50)
+        setTimeout(() => {
+          exit()
+          process.stdout.write("\n")
+        }, 50)
       }
       return
     }

apps/landing/src/pages/about.astro

@@ -32,10 +32,10 @@ const jsonLd = [
 
   <h2>what changed</h2>
   <p>
-    seo optimized for ranking algorithms. those algorithms read your <code>title</code>
-    tag, your headings, your link graph, and ranked you. you could rank well
-    while serving a single-page javascript app, because the crawler eventually
-    rendered it.
+    <dfn><strong>seo</strong></dfn> is a discipline that optimized for ranking
+    algorithms. those algorithms read your <code>title</code> tag, your headings,
+    your link graph, and ranked you. you could rank well while serving a
+    single-page javascript app, because the crawler eventually rendered it.
   </p>
   <p>
     generative engines work differently. they fetch your page, parse the html,
@@ -47,11 +47,11 @@ const jsonLd = [
 
   <h2>how the score works</h2>
   <p>
-    <a href="/">agentimization</a> samples up to 10 pages of your site, then runs
-    36 checks against the html, http headers, and well-known files. each check
+    <a href="/">agentimization</a> samples up to <strong>10 pages</strong> of your site, then runs
+    <strong>36 checks</strong> across <strong>8 categories</strong> against the html, http headers, and well-known files. each check
     returns one of: <strong>pass</strong>, <strong>warn</strong>, <strong>fail</strong>,
     <strong>skip</strong>, or <strong>info</strong>. checks are weighted by how
-    much they affect ai-readability.
+    much they affect ai-readability. a typical run completes in under <strong>15 seconds</strong>.
   </p>
   <p>
     the weighted average becomes a 0 to 100 score, mapped to a letter grade:

packages/core/src/checks/geo-signals.ts

@@ -188,10 +188,13 @@ const topicalAuthoritySignals: CheckDefinition = {
     let totalInternalLinks = 0
     let pagesWithGoodLinking = 0
 
+    // file:// urls have origin "null" so use href as the resolution base in local mode
+    const resolveBase = ctx.mode === "local" ? ctx.baseUrl.href : ctx.baseUrl.origin
+
     for (const page of pages) {
-      const links = extractLinks(page.html, ctx.baseUrl.origin)
+      const links = extractLinks(page.html, resolveBase)
       const internalLinks = ctx.mode === "local"
-        ? links.filter((l) => !l.startsWith("http://") && !l.startsWith("https://"))
+        ? links.filter((l) => l.startsWith("file:"))
         : links.filter((l) => {
             try {
               return new URL(l).origin === ctx.baseUrl.origin
@@ -312,7 +315,9 @@ const eeatSignals: CheckDefinition = {
 
       // expertise markers
       const hasCredentials = /Ph\.?D|M\.?D|CPA|certified|licensed|expert|specialist/i.test(page.html)
-      const hasAboutPage = extractLinks(page.html, ctx.baseUrl.origin).some((l) => /about|team|author/i.test(l))
+      // file:// origin is "null" so use href in local mode
+      const linkBase = ctx.mode === "local" ? ctx.baseUrl.href : ctx.baseUrl.origin
+      const hasAboutPage = extractLinks(page.html, linkBase).some((l) => /about|team|author/i.test(l))
 
       if (hasCredentials || hasAboutPage) withExpertise++
     }