Skip to content
Security Integrations Features Pricing Use Cases Learn Blog Log In Start Free Trial Search
Internal report

SEO audit

Pre-build state of infonet.co, gaps identified, and the prioritized plan that drove the May 2026 build.

Internal report. Not indexed by search engines. Share by sending the URL.

Infonet.co — SEO Audit (May 9, 2026)

Snapshot of where infonet.co stood before the May 9 SEO build, the gaps identified, and the prioritized plan that drove the work.


Pre-build state

AreaPre-state
Total HTML pages71 (excluding admin / video / newsletter-api / backups)
SitemapYes, but only ~50 URLs listed (28% under-coverage)
robots.txtPresent, correctly excludes admin/video/newsletter-api
Google AnalyticsNot installed anywhere
Google Search Console verificationNot present
Canonical tagsPresent on most pages but missing on homepage, contact, privacy, ship-log
H1 on homepageMissing (3 H1s inside slider, no static H1 visible to crawlers)
Open Graph + Twitter cardsYes, decent baseline
JSON-LD structured dataPresent on home (4 blocks) but inconsistent across rest of site
BreadcrumbList schemaNot present
Organization / WebSite schemaInconsistent
FAQ schemaNot present (homepage has 8 FAQ items, no schema)
Internal linking depthExisting posts cross-linked among themselves, but no link out to deeper resource taxonomy
Content footprint30 blog posts, 21 vs-competitor pages, 5 playbooks, 5 resources, 5 main pages
Page speed postureReasonable — gzip on, 30-day cache for static, font preconnect, lazy-loaded images
Security headersX-Content-Type-Options nosniff present (good baseline)
Mobile responsiveYes
AccessibilityDecent — aria-hidden on decorative SVG, alt text on most images

Gaps identified (in priority order)

  1. No analytics — flying blind on traffic, queries, conversions.
  2. No GSC verification — can't see ranking queries, indexing health, or click-through rates from Google.
  3. Homepage missing H1 — fundamental on-page SEO miss for the highest-traffic page.
  4. Sitemap incomplete — Google can't find ~30% of pages efficiently.
  5. Inconsistent structured data — missing Organization, BreadcrumbList, FAQ, Article schema across most pages.
  6. No long-tail content cluster — no glossary, no industry-vertical landing pages, no buyer-intent pages (pricing, alternatives, compliance).
  7. Existing posts not cross-linking to topic clusters — flat link graph; difficult for Google to identify topical authority.
  8. No FAQ schema on homepage — leaving SERP rich-results on the table for 8 high-quality FAQ items already on the page.

Plan executed

The May 9 build addressed all 8 gaps in a single push:

#ActionPages affected
1Install GA4 (G-W8ZGCMYRCN) site-wide71 → now 116
2Add canonical tags to all pages with URL derived from path116
3Add Organization + WebSite + SoftwareApplication JSON-LD via @graph116
4Add BreadcrumbList JSON-LD to every non-home page115
5Add visually-hidden semantic H1 to homepage; demote slider H1s to H21
6Build /use-cases/ hub + 8 industry pages (agencies, recruiting, SaaS, founders, real estate, financial advisors, consultants, sales teams)9 new
7Build /glossary/ hub + 25 long-tail term pages26 new
8Write 10 new high-intent blog posts (pricing, compliance, tactics, data)10 new
9Inject "More on this topic" link section into all 30 existing blog posts30
10Surface 10 new posts on /blog/ index1
11Add FAQPage schema mirroring the 8 homepage FAQ items1
12Regenerate sitemap covering all 116 pages1

Why this set, in this order

  • Foundation first. Analytics + canonicals + sitemap + H1 are the technical baseline. Without them, every later action is harder to measure or bound.
  • Schema next. Organization, BreadcrumbList, and FAQ schema are cheap to add and unlock SERP features (rich snippets, breadcrumb display, knowledge-panel candidacy).
  • Content cluster building. /use-cases/ and /glossary/ create topical authority around the LinkedIn automation domain. Each new page is a node in the topical graph that signals "Infonet covers this domain comprehensively."
  • Internal linking last. Once new content existed, every existing post was wired to point at it. This both surfaces the new content to the crawler quickly and lifts old posts via topical depth.

Out-of-scope for this round

The following were considered and deferred:

  • Image optimization (WebP/AVIF for blog images). Existing blog images are already PNG with lazy-loading. WebP conversion is a 3-4 hour job for the 13 MB blog/images directory; modest performance benefit; no SEO impact in 2026 (Google switched off mobile-friendly explicit ranking signal in 2024).
  • Schema for VS / comparison pages. Each /vs/ page could carry a Product or SoftwareApplication comparison schema. Worth doing in a future pass; current Organization schema is sufficient for Knowledge Graph candidacy.
  • AMP. Deprecated by Google as a ranking signal in 2021; not worth implementing.
  • Hreflang. Site is English-only; no hreflang needed until a localized version ships.
  • Backlink outreach / off-page SEO. Out of scope for an on-page SEO sprint.
  • Submit to Google Search Console + Bing Webmaster Tools. This is a one-click manual step you'll do after this push (sign in, add property, verify via DNS or HTML tag, submit sitemap).

Verification commands

Run any of these from your laptop to confirm the changes are live:


# GA4 installed
curl -s https://infonet.co/ | grep -c "G-W8ZGCMYRCN"   # should print 2

# Schema present on a blog post
curl -s https://infonet.co/blog/linkedin-100-invite-limit/ | grep -c "application/ld+json"   # 4

# Sitemap covers all pages
curl -s https://infonet.co/sitemap.xml | grep -c "<url>"   # 116

# New use-cases hub
curl -sI https://infonet.co/use-cases/ | head -1   # 200 OK

# New glossary hub
curl -sI https://infonet.co/glossary/ | head -1   # 200 OK

# Single H1 on homepage
curl -s https://infonet.co/ | grep -c "<h1"   # 1

Next manual steps (5 minutes)

  1. Sign in to Google Search Console with an account that has access to infonet.co
  2. Add property https://infonet.co (or confirm existing)
  3. Submit sitemap: https://infonet.co/sitemap.xml
  4. Same for Bing Webmaster Tools (https://www.bing.com/webmasters)
  5. Confirm GA4 property G-W8ZGCMYRCN is receiving traffic — should be visible in real-time within 5 minutes of any page load.

That's it. The technical SEO floor is now solid; rankings improve over the next 4-12 weeks as Google recrawls.