How the four A Square Solutions properties connect operationally — entity architecture, GEO relationship mapping, cross-domain authority, and canonical structure.
This document defines how the A Square Solutions ecosystem operates as a unified entity across four properties. It covers structural relationships, GEO/AI-search entity architecture, cross-domain authority strategy, and the canonical/sitemap framework that binds them.
Four properties. One entity.
| Property | Domain | Platform | Role |
|---|---|---|---|
| Main site | asquaresolution.com | WordPress | Parent entity — agency presence, services, authority base |
| AI Execution Lab | lab.asquaresolution.com | Next.js / Vercel | Operational transparency layer — systems, docs, public work journal |
| TrustSeal | trustseal.asquaresolution.com | React / GitHub Pages | AI trust verification product — proves website credibility |
| ScamCheck | scamcheck.asquaresolution.com | React / GitHub Pages | AI scam detection product — protects users from deceptive sites |
All four are subdomains of asquaresolution.com. Google treats subdomains as separate properties for ranking purposes, but the shared domain root and cross-linking create entity coherence that AI search systems can parse.
Each property has a different function, but one shared story:
A Square Solutions builds AI-native systems in public. The products (TrustSeal, ScamCheck) are real production software built and operated by the same team that documents the work in the Lab. The main site is the entity anchor.
This is the story AI search systems should be able to extract. The narrative works because it's true — not because it's been engineered. The integration work makes it structurally legible.
AI search engines (ChatGPT, Perplexity, Claude, Gemini) build entity graphs from:
sameAs and publisher declarationsEvery property must use these exact strings wherever the entity is named:
| Field | Required Value |
|---|---|
| Organization name | A Square Solutions |
| Main domain | https://asquaresolution.com |
| Lab URL | https://lab.asquaresolution.com |
| TrustSeal URL | https://trustseal.asquaresolution.com |
| ScamCheck URL | https://scamcheck.asquaresolution.com |
| Twitter handle | @asquaresolution |
| Twitter URL | https://twitter.com/asquaresolution |
Acceptable variants that don't break entity mapping:
Not acceptable (breaks entity mapping):
The Organization schema must appear on all four properties. The sameAs array on each property should reference all ecosystem URLs:
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "A Square Solutions",
"url": "https://asquaresolution.com",
"description": "AI execution, GEO/AI-search strategy, and production WordPress engineering.",
"sameAs": [
"https://asquaresolution.com",
"https://lab.asquaresolution.com",
"https://trustseal.asquaresolution.com",
"https://scamcheck.asquaresolution.com",
"https://twitter.com/asquaresolution"
]
}
Current status:
app/layout.tsxindex.html <head> as inline <script type="application/ld+json">TrustSeal and ScamCheck should each have SoftwareApplication schema in addition to Organization:
{
"@context": "https://schema.org",
"@type": "SoftwareApplication",
"name": "TrustSeal",
"applicationCategory": "SecurityApplication",
"operatingSystem": "Web",
"description": "AI-powered website trust verification and fact-checking tool.",
"url": "https://trustseal.asquaresolution.com",
"author": {
"@type": "Organization",
"name": "A Square Solutions",
"url": "https://asquaresolution.com"
}
}
This signals to AI search systems that these are real products built by a named entity, not content pages.
Links flow both up and across the ecosystem:
asquaresolution.com ←→ lab.asquaresolution.com
↑ ↕
trustseal.asquaresolution.com ←→ scamcheck.asquaresolution.com
WordPress → Lab (high priority): WordPress posts with AI, SEO, and automation topics link to relevant Lab content. This passes authority from the established domain to the newer Lab subdomain.
Lab → WordPress (consistent): All Lab content credits A Square Solutions with a link to the main site. This reinforces the parent-entity relationship.
Lab → Products (contextual): Lab content in relevant topic areas references TrustSeal and ScamCheck as real examples of AI products built by the same team.
Products → Lab (trust signal): TrustSeal and ScamCheck footers link to the Lab as proof that the builder works publicly and transparently.
Products → WordPress (authority anchor): All product footers and About sections link to asquaresolution.com as the parent.
Each property uses absolute canonical URLs pointing to its own domain. No cross-domain canonicals.
| Property | Canonical pattern |
|---|---|
| WordPress | https://asquaresolution.com/[slug] |
| Lab | https://lab.asquaresolution.com/[section]/[slug] |
| TrustSeal | https://trustseal.asquaresolution.com (SPA — one canonical) |
| ScamCheck | https://scamcheck.asquaresolution.com (SPA — one canonical) |
Cross-domain canonical pointing (e.g., TrustSeal canonical pointing to WordPress) would signal to Google that one property is a duplicate of the other. Never do this.
Each property maintains its own sitemap:
https://asquaresolution.com/sitemap_index.xml (Rank Math)https://lab.asquaresolution.com/sitemap.xml (Next.js app/sitemap.ts)sitemap.xml or submit single URLSitemap cross-references are not standard practice and should not be used. Each sitemap covers its own property only.
Google Search Console: Each subdomain should be a separate property in Search Console, verified independently. The shared GA4 property already handles cross-domain tracking.
Function: Establishes A Square Solutions as a real organization with services, expertise, and history. This is where prospective clients, journalists, and AI crawlers go to understand what A Square Solutions is.
Integration requirements:
Function: Documents real production work publicly. This is the property that earns citations from AI search systems — because it contains specific, verifiable, entity-dense content about real systems.
Integration requirements:
Function: Gives businesses a way to verify and display AI-assessed trust scores. Generates revenue via Razorpay. Credibility is its core value proposition.
Integration requirements:
Function: Lets users check URLs and businesses for scam signals using AI. Free tool with virality potential.
Integration requirements:
For AI search systems to consistently cite A Square Solutions content, the entity needs to appear in multiple independent contexts on authoritative topics.
Stage 1 (current): Lab is live. Organization schema present. Content is entity-dense.
Stage 2 (implement now): WordPress adds Lab references. Products add Lab footer links. Organization schema updated on all four properties with full sameAs array.
Stage 3 (ongoing content): Lab case studies explicitly document TrustSeal and ScamCheck build history. This creates real, citable content about real products — the highest-value GEO signal.
Stage 4 (eventual): When AI systems search for information about AI scam detection, trust verification, or AI-powered content operations — A Square Solutions appears as the named entity behind real products with documented build histories.
The Lab's specific content (failure reports with exact error messages, systems with specific tool names and versions, playbooks with real workflow steps) is the type of content AI retrieval systems score highly. A generic business site rarely gets cited. A site with documented production failures, real build logs, and specific operational data does.
The product references within Lab content (TrustSeal, ScamCheck) connect those entity names to specific, citable technical content — giving AI systems a reason to mention those products when relevant queries arise.
Execute in this sequence:
sameAs array<head><head>