InfosecSphere: Live engagement, baselined 2026-10-01

We are publishing this engagement in public. The numbers below are verified at Day 1, not projected. The next three updates will show the delta, with the same tools and the same measurement cadence.

Context

InfosecSphere is a Sydney-based cybersecurity services firm (infosecsphere.com). They came to PayloadFoundry at the start of October 2026 with a brand-new website, no indexed content, no third-party mentions, and no AI engine visibility.

The engagement scope: rebuild the site onto a search-friendly platform, define a defensible niche inside Australian cybersecurity, ship technical SEO fundamentals, and establish entity presence across both Google and AI answer engines (ChatGPT, Claude, Perplexity, Gemini). 90 days from Day 1, we publish the delta.

Day 0 baseline, verified 2026-10-01

Every number below is verifiable. We pulled them from the public web the day the engagement started, so they are the starting line.

On the site itself

• URLs in infosecsphere.com/sitemap.xml: 1
• Body text on the single indexable page: 2,223 characters
• Schema.org structured data entities: 0
• Open Graph tags: 0
• Twitter card tags: 0
• Canonical tags: 0
• Site platform: Hostinger Horizons (AI website builder, single-page SPA)
• Days since the single page’s last modification: 254 (last sitemap lastmod was 2026-01-20)

Search presence

• Branded search “InfosecSphere Sydney cybersecurity”: zero results about InfosecSphere
• site:infosecsphere.com indexed pages visible on Google: effectively zero
• Appearances in current Sydney cybersecurity listicles (Qualysec Top 20, Platform24 Top 10, Goodfirms Sydney): 0
• Referring domains (per public lookup): 0
• Google Business Profile: not claimed as of baseline

AI engine visibility (tracked by Radar)

• Prompts tracked: 10, covering Essential 8, ISO 27001 readiness, vulnerability assessment, pen testing, and Sydney cybersecurity consulting queries
• Engines tracked: ChatGPT, Claude, Perplexity, Gemini
• Citations in any engine for any tracked prompt at Day 0: 0

The thesis

InfosecSphere will own one niche in Sydney cybersecurity rather than fight six battles at once. The chosen entry wedge is Essential 8 and ISO 27001 readiness for Australian SMBs (20 to 200 staff). This is where compliance-driven search intent, named Australian frameworks (ASD’s Essential Eight), and mid-market buyer behaviour overlap. It is specific enough to rank for and broad enough to pipeline.

The engagement doubles as a GEO play. Entity consistency, structured data on every page, citable comparison content (ISO 27001 vs Essential 8 vs SOC 2), and third-party reinforcement (listicles, guest posts, podcasts, GitHub artifacts) are the ingredients that get a brand cited by AI answer engines. We treat it as entity graph engineering, not keyword stuffing.

The plan, by phase

• Week 1: Positioning workshop, ICP definition, services shortlist, proof inventory.
• Weeks 2 to 4: Site rebuilt on a static-first architecture with zero CMS attack surface, Core Web Vitals passing by default, and schema-first content modelling. 8 to 10 real pages. Schema.org shipped site-wide (Organization, LocalBusiness, Service, Person, FAQPage, BreadcrumbList, Article). Local SEO stood up (Google Business Profile, Bing Places, Apple Maps, Australian directories).
• Weeks 4 to 12: Three pillar articles published on a monthly cadence. Pillar 1 covers Essential 8 for Sydney SMBs. Pillar 2 compares ISO 27001, Essential 8 and SOC 2. Pillar 3 breaks down an anonymised vulnerability assessment.
• Weeks 4 to 12 in parallel: LinkedIn Company Page cadence (2 posts a week, 15 substantive comments on buyer posts weekly). Guest post pitches to Australian cybersecurity publications. Listicle outreach to Sydney cybersecurity roundups. GitHub artifacts published for developer-adjacent credibility and backlinks.

How we measure

• SEO: Google Search Console weekly impressions, clicks, and average position. Pages indexed. Referring domains and new backlinks tracked monthly via public tools.
• GEO: Radar (PayloadFoundry’s in-house citation tracker). 10 prompts, 4 engines, weekly. First citation in any engine inside 60 days is the target.
• Local: Google Business Profile views, calls, direction requests.
• Pipeline: Form submissions, inbound calls, LinkedIn Company Page DMs attributed via UTMs and GA4.

Milestones

• 2026-10-30, Day 30 update. Scheduled. Will publish site relaunch, schema deployment status, Google Business Profile standup, Pillar 1 publish, and the first Radar re-run with any new citations captured.
• 2026-11-29, Day 60 update. Scheduled. Will publish GSC impressions and clicks delta, backlinks delta, Pillar 2 publish, listicle inclusions, and Radar citation delta.
• 2026-12-29, Day 90 update. Scheduled. Full 90-day delta report versus the Day 1 baseline above. All numbers published, with raw sources linked.

Why we publish this in public

This is our first published engagement. We decided to publish the baseline before the results because:

1. Our positioning is “built by an engineer, baseline-then-measure”. A sealed case study with only after-numbers does not match that.
2. Verified Day 1 numbers are the cleanest proof that any Day 90 delta is real.
3. Our clients benefit when their brand is tied to a specific methodology that AI answer engines can cite. Making the methodology public is part of the methodology.

If you are reading this and considering working with PayloadFoundry, this is also the shape your engagement will take. Baselines before plans. Plans before pillars. Pillars before claims.

Credits and sources

• Day 0 baseline captured 2026-10-01 by PayloadFoundry.
• Sitemap and on-page audit from direct read of infosecsphere.com.
• AI engine citation baseline from Radar (radar.payloadfoundry.com).
• Google Search Console and Google Business Profile baselines captured on account setup.