Aemorph's technical SEO opens every core page of your site to Google and the AI crawlers, so your pages qualify to rank in search and be quoted in AI answers.
Buyers shortlist the businesses they find, and being found is where your leads and sales start. Aemorph finds what blocks crawlers, specifies each fix for your developers and verifies it once live. Technical SEO runs on the LLM Influencer System, Aemorph's SEO, AEO and GEO programme, with additions tailored to your site's technical health. Organic growth compounds: BizCover grew organic traffic 4,820% across nearly eight years with Aemorph's team.
Thirteen-area technical SEO audit · Strategic conversation free, 30 to 60 minutes · Aemorph responds within 24 hours
Written by Kevin Dam, founder of Aemorph, who has practised SEO since 2010 and sits on the Forbes Agency Council. Aemorph is a Google Partner. LinkedIn
Technical SEO Removes What Stops Your Pages Being Found
Aemorph's technical SEO removes the faults that keep your pages out of Google and the AI chats, so the content and links you already pay for turn into rankings and traffic.
Aemorph specifies canonicals, redirects and hreflang, designs internal links as a semantic network and writes nested JSON-LD; your developers or IT vendor implement each change, and Aemorph verifies it. The work serves Singapore and Australian businesses whose buyers research before they buy.
A crawl with Screaming Frog, a tool that reads your site the way a search engine does, shows heading, canonical, redirect and indexing faults across every page template. Each fix is specified at the template, so one change by your developers corrects every page that uses it, and your developers set the pace. Core Web Vitals, Google's measures of loading speed, responsiveness and visual stability, are measured against Google's good thresholds: a Largest Contentful Paint within 2.5 seconds, an Interaction to Next Paint of 200 milliseconds or less and a Cumulative Layout Shift of 0.1 or less.
| Deliverable | The problem it solves | What changes for you | Surface | Delivered through |
|---|---|---|---|---|
| Crawl and index access for core pages | Core service pages blocked by robots.txt, a stray noindex or an incorrect canonical | Every core page open to crawling and indexing | Google Search, AI Overviews | Audit, then fix work scoped from the findings |
| Canonical, redirect and hreflang configuration | Duplicate URLs, migrations redirected to the homepage, Singapore and Australian versions competing | One canonical URL per page, one-to-one redirects, reciprocal hreflang | Google Search | Audit, then fix work scoped from the findings |
| AI crawler access policy | robots.txt blocks the wrong crawler, or core content appears only after JavaScript runs | robots.txt rules that open the pages you choose to the search crawlers of OpenAI, Anthropic and Perplexity, with core content served without JavaScript | ChatGPT search, Claude, Perplexity | Audit, then fix work scoped from the findings |
| Internal links as a semantic network | Key pages sit more than 3 clicks deep | Parent, child and peer pages link in a structure crawlers follow | Google Search, AI engines | Fix work, then a monthly package |
| Nested JSON-LD structured data | Basic organisation schema often states little beyond a name and a logo | Your organisation, people, services and evidence connected in one machine-readable graph | Google AI Overviews and Bing, which read schema | Fix work, or Entity Hardening (Sprint 2), Aemorph's technical entity SEO sprint |
| Core Web Vitals and mobile usability | Slow or unstable pages | Pages measured against Google's good thresholds | Google Search | Audit, then monitored |
Source: Google Search Central, Core Web Vitals, 2025.
What the technical SEO audit checks
Aemorph's technical SEO audit checks thirteen areas of your site, from crawl and index controls to AI crawler access.
It carries no keyword research and no keyword opportunities. Fix work afterwards is scoped and quoted from the findings, because the work depends on what the audit finds.
| Area | Checks | Tool | Why it matters | Output |
|---|---|---|---|---|
| Crawl and index | robots.txt named and formatted correctly and listing the sitemap; an XML sitemap holding only SEO-relevant pages, declared in robots.txt and submitted to Google Search Console and Bing Webmaster Tools; each page indexed or kept out of the index as intended; crawl stats | Google Search Console, Bing Webmaster Tools, Screaming Frog | A crawl block stops that crawler fetching the page's current content | Index status for each page against the intended status |
| Single-version URLs | http, https, www and non-www resolve to one HTTPS version | Screaming Frog | Several live versions split one page's signals | The versions that fail to resolve to one URL |
| Canonical tags | Canonical tags present and pointing at the intended URL | Screaming Frog | Google reads the canonical as a strong signal for which URL to index | Pages with missing or conflicting canonicals |
| Status codes and redirects | Status codes, redirect chains and broken links | Screaming Frog, Ahrefs | Chains and broken links waste crawl and lose visitors | A list of chains and broken links to repair |
| Architecture | Each page within 4 clicks, orphan pages, internal links, parameters, pagination and URL structure | Screaming Frog | This check identifies weak internal discovery paths and disconnected pages | Deep pages, orphan pages and structural faults |
| Duplicates | Duplicate pages, titles, meta descriptions and H1s | Screaming Frog | Duplicates leave search engines to choose between competing pages | Duplicate sets grouped by template |
| Speed | Core Web Vitals, render-blocking resources and image weight | Lighthouse, Google Search Console | Google publishes good thresholds for Core Web Vitals | Templates that miss the thresholds |
| Mobile and rendering | Mobile usability and JavaScript rendering | Lighthouse, Screaming Frog | Content that appears only after JavaScript runs stays unread by crawlers that skip JavaScript | Pages whose content depends on JavaScript |
| Hreflang | Hreflang where the site serves more than one market | Screaming Frog | Google ignores hreflang pairs that do not point to each other | Missing or one-way hreflang pairs |
| Structured data | Presence and validity of structured data | Screaming Frog, DataForSEO | Google AI Overviews and Bing read schema | Missing and invalid markup by template |
| Security | A valid SSL certificate and mixed content | Lighthouse, Screaming Frog | HTTPS is one of the technical minimums | Certificate status and mixed-content pages |
| Link health | Broken backlinks and backlinks to dead or redirected pages | Ahrefs | Links to dead pages carry no value to the live site | Backlinks to reclaim with redirects |
| AI crawler access | Robots rules for GPTBot, ClaudeBot, PerplexityBot and Google-Extended; llms.txt | Screaming Frog, DataForSEO | The crawler policy sets permissions for named crawlers, with separate controls for training and search | The current policy for each AI crawler token |
Audit tools: Lighthouse, DataForSEO, Ahrefs, Screaming Frog, Google Search Console and Bing Webmaster Tools.
What is technical SEO?
Technical SEO is the discipline that makes a website crawlable, indexable and machine-readable, so the core pages are open for Googlebot and AI crawlers to fetch and read, and eligible for Google to render and index.
It covers robots.txt (the file that tells crawlers, the bots that read websites, which pages they are allowed to read), canonicals (tags naming the main version of a page), redirects, hreflang (tags that match each page to its language or market), internal links, structured data, Core Web Vitals and HTTPS. A crawl block stops that crawler fetching the page's current content; content it indexed earlier, and other sources, are a separate matter.
What does technical SEO include?
Technical SEO includes eight controls: editable titles, headings and URLs; indexable core pages free of robots.txt blocks, noindex tags and wrong canonicals; configurable redirects, canonicals and hreflang; JSON-LD structured data; acceptable Core Web Vitals and mobile usability; HTTPS; working analytics; and an architecture that supports hub pages and internal links.
Aemorph checks all eight before the first fix, because a platform that locks any of them caps what the technical work achieves.
How to fix technical SEO issues?
Technical SEO issues get fixed in a set order, starting with a full crawl that finds the errors, then triage that ranks them by impact, then repairs at the template rather than page by page; Aemorph specifies each repair, your developers or IT vendor implement it, and Aemorph verifies it.
Three corrections recur across Aemorph's audits:
- Consolidates duplicate intent into one exhaustive page and points the duplicates at it with 301 redirects.
- Moves extra H1 tags out of templates, replacing unnecessary heading tags with CSS or div elements.
- Removes indexed staging URLs, test versions of your site, from Google with noindex or a removal request, redirects them where a live replacement exists and puts staging behind a login.
Why Crawl and Index Access Come Before Speed-Score Fixes
Crawl and index access come before speed-score fixes because a fast page still wins no rankings or traffic when crawlers have no access to it or read it incorrectly.
AI keeps a map of what every business is and what it does. Each AI engine answers from what it has learned and looked up about a business across many sources; your website is one of them, and technical SEO keeps it open and readable.
Aemorph's technical scope extends beyond page speed, crawl-error lists and basic organisation schema to search and AI crawler access, canonical signals that agree, internal links that connect related pages by topic, and nested JSON-LD, code that describes how your business works in a format Google and Bing read. Aemorph's audits turn up broken canonicals, incorrect redirects and indexing errors left unfixed.
Google treats rel="canonical" and redirects as strong canonical signals and sitemap inclusion as a weak one, and it sometimes indexes URLs that robots.txt disallows, without their content, so robots.txt is the wrong tool for choosing a canonical URL. Google recommends JSON-LD among the three structured data formats it supports, and JSON-LD 1.1 has been a W3C Recommendation since 16 July 2020.
Source: Google Search Central, Consolidate duplicate URLs, 2026, and Intro to structured data, 2025; W3C, JSON-LD 1.1, 2020.
| Checklist fix | What a crawler still misses | What Aemorph specifies instead | Evidence standard | Where it gets fixed |
|---|---|---|---|---|
| Page speed score | A fast page with a crawlable noindex stays out of Google's index; robots.txt blocks crawling, not URL-only indexing | Crawl and index access checked before speed | Google Search Central, robots.txt introduction (2025) | robots.txt, meta robots |
| Canonical tags added | A canonical that differs between raw and rendered HTML; Google reads a canonical tag as one strong signal among several | Canonical tag, redirects and sitemap all name the same URL | Google Search Central (2026) | Templates, server |
| Basic organisation schema | A name and a logo, with no services, people or evidence | Nested JSON-LD across organisation, people, services, locations and evidence | Google Search Central (2025); W3C JSON-LD 1.1 (2020) | Templates, CMS |
| Crawl-error list cleared | Key pages still more than 3 clicks deep | Internal links built as parent, child and peer relationships | Aemorph audit threshold | Navigation, templates |
| Hreflang tags added | Language versions that do not list each other break Google's hreflang requirement | Reciprocal hreflang with an x-default fallback | Google Search Central (2026) | Head tags, HTTP headers or sitemap |
Sources: Google Search Central documentation on robots.txt, canonicals, structured data and hreflang; W3C JSON-LD 1.1.
The technical layer sits under the wider search work, and Aemorph's SEO services extend this technical layer into content and off-site reinforcement.
What is the difference between SEO and technical SEO?
The main difference between SEO and technical SEO is scope: SEO covers everything that earns visibility, including content, entities and off-site reinforcement, while technical SEO covers the infrastructure that lets crawlers fetch, render and index those pages.
Technical SEO is the base layer that content and links depend on for index eligibility. Specialist services build on the same base, and ecommerce SEO structures product and category records on top of it.
Why is technical SEO important?
Technical SEO matters because it establishes crawl access, index eligibility and readable first-party content for search engines and AI engines.
Google lists a page as a supporting link in AI Overviews only when the page sits in Google's index and is eligible for a snippet, the short extract shown in results. In Vercel's December 2024 network study, OAI-SearchBot, ChatGPT-User, GPTBot and ClaudeBot rendered no JavaScript in the traffic observed, so those bots missed any content that appeared only after JavaScript ran.
Source: Google Search Central, AI features and your website, 2025; Vercel, The rise of the AI crawler, 17 December 2024.
What are some examples of technical SEO?
Technical SEO examples include fixing robots.txt rules that block core pages, setting canonical tags on duplicate URLs, mapping one-to-one 301 redirects during a migration, adding hreflang for Singapore and Australian versions, removing duplicate H1 tags from templates, server-rendering JavaScript content and publishing nested JSON-LD structured data.
One-to-one redirects keep old URLs from landing on the homepage, and server rendering lets crawlers that skip JavaScript still read your content.
The technical SEO audit finds these issues before any fix begins, and for the commercial case the Money on the Table audit estimates the revenue a business is leaving on the table in search.
Technical SEO for AI crawlers
Technical SEO for AI crawlers separates the crawlers that put your site into AI search answers from the crawlers that collect training data, then makes sure the first group reads your core pages without JavaScript.
OpenAI runs OAI-SearchBot to surface sites in ChatGPT search and GPTBot to collect training content, and each follows its own robots.txt rule, so blocking GPTBot signals that your content stays out of training without removing your site from ChatGPT search. Anthropic runs ClaudeBot for training data and Claude-SearchBot for Claude's search results, and both honour robots.txt. PerplexityBot surfaces and links sites in Perplexity search, and Perplexity does not use it for model training. Google-Extended is a robots.txt token rather than a crawler: it controls whether your crawled content trains future Gemini models and supports Gemini answers, and it has no effect on Google Search inclusion or ranking. GPTBot was named in 4.5% of desktop robots.txt files in 2025, up from 2.9% in 2024.
The technical SEO audit records your robots rules for GPTBot, ClaudeBot, PerplexityBot and Google-Extended and whether an llms.txt file exists; OpenAI, Perplexity and Anthropic have not confirmed that their engines read llms.txt. The crawler policy stays your decision: Aemorph specifies the robots.txt rules for the policy you choose and verifies them once your developers publish them.
Source: OpenAI crawler documentation, September 2026; Anthropic, Claude Help, 7 April 2026; Perplexity crawler documentation; Google's common crawlers documentation, updated 14 July 2026; HTTP Archive, Web Almanac 2025.
| Crawler (robots.txt token) | Operator | What it does | Controlled through robots.txt | Effect of blocking it |
|---|---|---|---|---|
| Googlebot | Crawls for Google Search, including AI Overviews | Yes | Google stops crawling the page; the URL sometimes stays indexed without its content | |
| Google-Extended | Token governing whether crawled content trains future Gemini models and grounds Gemini answers | Yes (token only, no separate crawler) | No effect on Google Search inclusion or ranking | |
| OAI-SearchBot | OpenAI | Surfaces sites in ChatGPT search | Yes | The site leaves ChatGPT search answers; navigational links sometimes still appear |
| GPTBot | OpenAI | Crawls content that trains OpenAI models | Yes | Signals the content stays out of model training |
| ClaudeBot | Anthropic | Collects content that trains Claude models | Yes | Signals that future content stays out of training datasets |
| Claude-SearchBot | Anthropic | Crawls to improve Claude's search results | Yes | Anthropic stops indexing the content for search |
| PerplexityBot | Perplexity | Surfaces and links sites in Perplexity search; not used for model training | Yes | Perplexity recommends allowing it for the site to appear in its search results |
User-initiated fetchers (ChatGPT-User, Claude-User, Perplexity-User) fetch a page when a person asks; OpenAI and Perplexity state that robots.txt rules do not always apply to them. Sources: OpenAI, Anthropic, Perplexity and Google crawler documentation, 2026.
Google runs a page's JavaScript in a separate step after crawling, and still recommends server-side rendering or pre-rendering, which deliver the full page without waiting for JavaScript. Google AI Overviews need no special schema and no AI text files, only an indexed page that is eligible for a snippet.
Source: Google Search Central, JavaScript SEO basics, 2026, and AI features and your website, 2025.
Broken structured data breaks the machine-readable labels a page publishes, not the reading of its visible text, and the schema markup errors guide diagnoses where structured data breaks.
Is SEO dead now with AI?
No, SEO is not dead; AI search depends on it.
Google requires a page to sit in its index and be eligible for a snippet before it appears as a supporting link in AI Overviews, and ChatGPT search surfaces sites through OAI-SearchBot, a crawler you control through robots.txt like any search bot. The same indexed, readable site is one of the sources the AI chats look up, and Generative Engine Optimisation reinforces the same facts inside the AI chats.
Aemorph runs SEO, AEO and GEO at the same time, in one content programme. SEO earns your place in Google's regular results. AEO, answer engine optimisation, gets you quoted in Google AI Overviews, featured snippets, answer boxes and voice answers. GEO, generative engine optimisation, gets you named and cited in AI chats such as ChatGPT, Claude, Gemini and Perplexity. The same pages are built to rank, to be quoted in Google's AI answers and to be cited in the AI chats. GEO work starts on day one, with sets of test prompts, a review of your structured data and an audit of how easily AI tools read and quote your pages, and it goes live once the content is published and the changes are in place.
The three Singapore agencies that quoted Aemorph in June 2026 gate or bundle GEO onto SEO. Source: agency quotes collected by Aemorph, June 2026.
Aemorph's Team Lifted Top 1 to 3 Rankings 612% Across Four Client Engagements
Aemorph's team grew top 1 to 3 keyword rankings by an average of 612% raw and 820% normalised to twelve months across 4 clients, and more page-one terms bring more of the buyers who search for what you sell.
Organic traffic arrives without a cost per click and keeps compounding while your site stays open and readable to crawlers.
| Return | What moves | Verified evidence | Period | Source |
|---|---|---|---|---|
| Operational | Ranking depth across the terms that define the category | Top 1 to 3 keyword rankings up an average of 612% raw and 820% normalised across 4 clients | Each engagement, normalised to twelve months | Ahrefs, verified Aug 2026 |
| Financial | Organic traffic and the enquiries it carries | BizCover organic traffic from 894 to 43,989 monthly visits, +4,820%, or 65% a year compounded | Dec 2015 to Sep 2023 | Ahrefs, verified Aug 2026 |
| Risk | Pages lost to crawl, index or rendering faults | Signals reviewed against Aemorph's working thresholds: positions 11 to 20, crawl depth over 3 clicks, duplicate H1 tags, indexed staging | During the technical SEO audit | Aemorph audit practice |
Whole-engagement organic search results from Aemorph's team and the SEO discipline the entity-first method grew from, not results from technical work alone and not AI citations. Keyword averages cover the four clients with ranking data (EZRA Clinic, Casa Dental, Eye Concepts and Linda Mandarin), over keyword windows of 10 to 11 months. Each result is normalised with the compound annual growth rate: (end / start) ^ (12 / months) minus 1. Source: Ahrefs, August 2026. How results are measured
Case study · Insurance broker platform, Australia
BizCover grew organic traffic 4,820% across nearly eight years.
Monthly organic visits rose from 894 to 43,989 between December 2015 and September 2023. That is a compounding figure, not an annual one: the annualised rate of 65% sits in the bottom third of Aemorph's portfolio. Read the BizCover case study, which documents the organic growth record
Organic search results, not AI citations. Source: Ahrefs, August 2026. How results are measured
Six signals trigger a technical review, each with a usual fix once the cause is confirmed. Across the wider web, 48% on mobile and 56% on desktop achieved a good overall Core Web Vitals result in June 2025, one of the figures Aemorph's statistics hub tracks with a source and year.
| Signal | Trigger threshold | What Aemorph checks for | Tool that shows it | Usual fix once confirmed |
|---|---|---|---|---|
| Keyword positions | Stuck between positions 11 and 20, the general pattern | Possible duplicate intent across pages (cannibalisation) or incomplete coverage, confirmed by URL overlap for the query | Ahrefs or Semrush, Search Console | Consolidate confirmed duplicates into one page and 301 them |
| Crawl depth | Key pages more than 3 clicks from the homepage | Weak internal linking | Crawl depth visualisation | Rebuild parent, child and peer links |
| H1 tags | More than one H1 per template (an Aemorph template convention) | Template markup that misstates the page hierarchy sitewide | Screaming Frog | Replace extra headings with CSS or div elements |
| Responsive headings | Separate heading tags for desktop, mobile and tablet | Duplicate H1, H2 and H3 tags | Screaming Frog | CSS breakpoints instead of duplicated markup |
| Staging | Test environments in a site: search | UAT or staging indexed | Google site: search | Noindex or remove the URLs, redirect where a live replacement exists, put staging behind a login |
| Migration | Rankings collapse after launch | Old URLs redirected to the homepage | Ahrefs, Semrush, Screaming Frog, Wayback Machine | One-to-one redirects, restore missing content |
The thresholds are Aemorph's own guidelines, not search engine requirements. Source for the Core Web Vitals figures: HTTP Archive, Web Almanac 2025.
“They tackled technical issues such as a misdirecting URL with professionalism and provided us with regular, clear updates.”
DeChengXinXing.comfamily wholesale importer of premium abalone, Singapore. Watch the video
Remarkable Furniture's technical restructure
Remarkable Furniture's organic traffic took off about four months after a technical restructure Aemorph advised, following about 18 months of flat traffic while the previous provider focused on backlinks.
Case study · Ecommerce (home furnishings), Australia
A database restructure ended 18 months of flat organic traffic.
Aemorph started work in September 2019. The store's database and product tables carried duplicate categories and subcategories, plus repeating keyword and product pages. Aemorph advised restructuring the database and product tables to consolidate them, with every old URL redirected to its correct new page, alongside the store's move from WordPress to Magento: 2,000+ pages from October 2019 to March 2020, six months in all. Monthly organic visits rose from 3,883 in September 2019 to 12,172 in October 2020, up 213%. Read the Remarkable Furniture case study, which documents the ecommerce record
| Stage | Period | What happened | Who acted | Source |
|---|---|---|---|---|
| Before Aemorph | About 18 months to Sep 2019 | Organic traffic flat while the previous provider focused on backlinks | Previous provider | Client account, Kevin Dam |
| Restructure and migration | Oct 2019 to Mar 2020 | Duplicate categories, subcategories and repeating pages consolidated; every old URL redirected to its correct new page; WordPress to Magento, 2,000+ pages | Aemorph advised the restructure | Aemorph project record |
| After implementation | About 4 months after launch | Organic traffic took off, reaching 12,172 monthly visits by Oct 2020 | Not applicable | Client account, Kevin Dam |
| Result | Sep 2019 to Oct 2020 | 3,883 to 12,172 monthly organic visits, up 213% | Not applicable | Ahrefs organic traffic |
Organic search result, not an AI citation. Source: Ahrefs (Australia), October 2020.
Aemorph's seven-step migration process
Aemorph plans your website migration in seven steps so your rankings and traffic carry over to the new site: Aemorph specifies the redirects, your developers or IT vendor implement them, and Aemorph verifies the result before and after launch.
- Existing URLs. Aemorph compiles every existing URL from Search Console, Ahrefs, Screaming Frog and the XML sitemap, with duplicates removed.
- Inbound links. Aemorph lists every URL that carries inbound links, drawn from Search Console, Ahrefs and Google Analytics.
- Rankings and sessions. Aemorph lists every URL with rankings and sessions, drawn from the same three sources.
- Consolidate. Aemorph merges the three lists with Search Console 404s, decides removals, decides whether each redirect is dynamic or manual and sends the remaining URLs to a custom 404 (page not found) page.
- Map and optimise. Aemorph maps key pages after keyword research and specifies their optimisation, covering information architecture, URL slugs, canonicals, titles, headings, alt text, meta descriptions, schema, breadcrumbs, the XML sitemap and robots.txt.
- Review design and implementation. Aemorph reviews proposed designs for on-page SEO structure and header tags, then checks that your developers implement the 301 redirects as planned.
- Post-launch monitoring. Aemorph monitors Search Console 404s, key-page uptime, Core Web Vitals, weekly Ahrefs crawls and analytics on the new site.
Five past migrations ran through this process, from 400+ to 4,000+ pages.
| Site | Pages | Platform move | Period | Outcome with source |
|---|---|---|---|---|
| Synapxe.sg | 4,000+ | Custom CMS to Sitecore | Launched Jul 2023 (project Mar to Aug 2023) | 6,372 monthly organic visits in Aug 2023, 21,953 in Mar 2024, up 245% |
| Remarkablefurniture.com.au | 2,000+ | WordPress to Magento | Oct 2019 to Mar 2020 | 3,883 monthly organic visits in Sep 2019, 12,172 in Oct 2020, up 213% |
| TWGTea.com | 2,500+ | Magento to custom CMS | 2018 | Held between 25,014 and 31,903 monthly organic visits through 2018 (Ahrefs, all countries, September 2026) |
| ePropulsion.com | 400+ | Wix to WordPress | Feb to Apr 2021 | 1,749 monthly organic visits in Dec 2020, 7,429 in Apr 2021 (Ahrefs, all countries, September 2026) |
| MyHeart.org.sg (Singapore Heart Foundation) | 1,500+ | WordPress to WordPress | Sep 2021 to Mar 2022 | Key-phrase rankings maintained and both project goals achieved (client statement, LinkedIn recommendation, 2 Jan 2023) |
Source: Ahrefs (all countries), September 2026. Ahrefs revises historical estimates, so these figures differ from the Australia-only figures above. Aemorph planned each migration and verified the result; the client's developers implemented it.
“The move included a complete rebuild of our website ePropulsion.com and it was crucial that we didn't lose any rankings. Through the guidance of Kevin and his team, we were able to successfully move to a more flexible WordPress platform and our scores on Ahrefs also increased.”
Flora LuoePropulsion
“Kevin and his team at Aemorph were assigned to work on the SEO migration efforts of the MyHeart.org.sg website in early 2022. [...] I'm happy that we engaged Kevin and his expertise as the goals of both were successfully achieved.”
Kheng Leng ChngMedia and Comms Professional, MyHeart.org.sg
Technical SEO Starts With a Free Call and a Crawl Audit
Technical SEO with Aemorph starts with a free strategic conversation and a crawl audit, so you see what holds back your rankings and traffic before you commit budget.
Aemorph then specifies the fixes, your developers implement them and Aemorph verifies them; Entity Hardening (Sprint 2), which builds the linked schema graph, follows where you choose it.
- Book a free strategic conversation of 30 to 60 minutes, a presentation on a video call that Aemorph recaps by email; Aemorph responds within 24 hours.
- Audit the crawl, render and index baseline with the technical SEO audit, covering the thirteen areas above.
- Specify each fix the findings call for, with development specifications and documentation for robots.txt, canonicals, redirects, hreflang, templates and JSON-LD.
- Verify each change after your developers or IT vendor implement it, against the specification and a fresh crawl.
- Continue, where you choose, into the Brand Codex, your brand fact sheet: the single source of truth for what AI says about you. The Showstopper Sensor (Sprint 1) publishes your approved showstopper answers as the LLM info page on your site; it is Aemorph's 30-day AI answer sprint on your showstopper questions, the buyer questions that stop a purchase when AI answers them badly. Entity Hardening (Sprint 2), the technical layer that tells search engines and AI who you are, builds the linked schema graph and the entity map, and a monthly package holds the technical layer across search and the AI chats.
Hreflang needs control of every language version, because each version lists itself and all the others. In 2025, robots.txt requests returned a success status on 84.9% of sites and a 404 on 13.3% of desktop sites, so the audit checks that file.
Source: Google Search Central documentation on localised versions, 2026; HTTP Archive, Web Almanac 2025.
| Prerequisite | Who does it | What Aemorph needs | Output | When |
|---|---|---|---|---|
| Strategic conversation (free) | Your decision-maker with Aemorph | 30 to 60 minutes on a video call | Confirmed scope | Aemorph responds within 24 hours |
| CMS capability check | Your web lead | Confirmation the CMS edits titles, meta descriptions, headings, URLs, internal links, canonicals, redirects, hreflang and JSON-LD, plus read or review access | Confirmed platform capability | From kick-off |
| Search Console, GA4 and Tag Manager access | Your marketing lead | Named user accounts with least-privilege access | Crawl, render and index baseline | From kick-off |
| Developer support | Your developers or IT vendor | Capacity to implement the template and server changes Aemorph specifies | Fixes live, then verified by Aemorph | After the audit |
| Sign-off on regulated claims | Your nominated point of contact | Sign-off on regulated statements | Approved public claims | Before Aemorph publishes |
| Entity Hardening (Sprint 2) | Aemorph, with your developers implementing | The website's content as scraped at kick-off | Source-of-truth record, linked schema graph, entity map and llms.txt | Up to 60 days, where chosen |
Who does the work on your technical SEO?
Your technical SEO runs with your own account manager and Aemorph's team: Kristine and Ryan, Senior SEO Specialists and Project Managers; Tent, Trinh, Wahyu and Minh, SEO Specialists; Michelle and Patrick, Content Specialists; Shiena, Web Project Manager; and Dom, Senior Web Developer.
Your account manager introduces the team members assigned to your account at kick-off, and every message gets a reply within 24 hours, in your business hours.
How long does technical SEO take to show results?
Your first ranking movements show within 45 days of publishing.
Google and the AI chats respond only to content that is live, so the 45 days count from publication, not from the start of your engagement.
Source: results reported in past client testimonials. Watch the client videos
How much does technical SEO cost?
Aemorph's technical SEO starts with a one-time audit, and Aemorph's work ranges from audits from S$1,000 one-time to enterprise monthly engagements from S$12,500 a month.
The specification and verification work after the technical SEO audit is scoped and quoted from the audit's findings, because that work depends on what the audit finds.
| Offer | Price |
|---|---|
| Audits | From S$1,000 one-time |
| Sprints | From S$5,000 per website |
| Influencer Blueprint (SEO strategy and roadmap) | From S$15,000 one-time |
| Entry monthly packages (Awaken, Anchor, Ascend) | S$2,500 to S$7,500 a month |
| Enterprise monthly engagements (Attain, Apex) | From S$12,500 a month |
Monthly packages are priced per market.
Want the most value for your budget and prefer to run the work in-house? Leveraged & Scalable, Aemorph's community, teaches your team to plan and execute SEO, AEO and GEO with AI tools, using the same skills and templates Aemorph's team works from. Below about S$5M in revenue, Aemorph recommends the community, and the first step is the free Hallucination Report, which compares what AI says about you with your website, or the free Money on the Table audit, both on tools.aemorph.com. Any business, at any size, buys Sprint 1 or Sprint 2 on its own, starting with the free strategic conversation. Full details are on the pricing page.
Buy the Showstopper Sensor (Sprint 1) on its own and it carries the Ground Truth Guarantee: if ChatGPT, Claude, Gemini and Perplexity still miss your approved facts 30 days after your answers go live, you get your Showstopper Sensor fee back in full. The five monthly packages, Awaken to Apex, carry the separate 45-day outline guarantee: within 45 days, you receive your complete Mathematical Market Monopoly outline, a plan of every topic and buyer question your market asks about, ready to implement yourself if you choose. Terms are set out in your quote.
| Offer | What it includes | Best suited to | Guarantee or delivery time | How to start |
|---|---|---|---|---|
| Technical SEO audit | The thirteen-area checklist, with no keyword research and no keyword opportunities | Sites whose core pages Google or AI crawlers fail to fetch, render or index | Within 21 days of kick-off | Request a quote |
| Technical SEO specification and verification | Development specifications and verification of your developers' implementation | Sites with fixes the technical SEO audit identifies | Scoped from the audit's findings | Follows the technical SEO audit |
| Money on the Table audit (free) | An estimate of the revenue you are leaving on the table in search | A business that wants a revenue figure before it commits budget | No charge | Free, on tools.aemorph.com |
| AEO-GEO Audit, a scored check of how AI engines see your business | AI crawler access, content crawlability, live AI search recall, training recall and visibility fragility, with a score out of 100 and a prioritised fix plan | An enterprise that needs the starting diagnostic | 21 days from kick-off | Offered at the end of the strategic conversation |
| ESAG audit, the enterprise SEO, AEO and GEO audit | Everything in the AEO-GEO Audit plus a site readiness audit with a crawl of up to 1,000 pages | Enterprise sites; Aemorph recommends it to most enterprise clients | Within 21 days of kick-off | Offered at the end of the strategic conversation |
| Hallucination Diagnostic | 50 to 150 prompts across the four AI engines, presented on a call; included in Sprint 1 and in both enterprise audits | A test of what the AI chats say about your business | Report in 5 business days | Request a quote |
| Showstopper Sensor (Sprint 1) | The showstopper questions, the approved answers published as the LLM info page, a report and a call | A business whose buyers get wrong answers from AI assistants | 30 days; the Ground Truth Guarantee when bought on its own | Request a quote |
| Entity Hardening (Sprint 2) | Source-of-truth record, linked schema graph, entity map, llms.txt, and an audit of your Wikidata and Google Knowledge Graph entries; Aemorph makes the Wikidata edits and submits the Google Knowledge Graph updates, and those edits do not always stay in place | A site that needs its schema and entity layer specified | Up to 60 days; no guarantee attached | Request a quote |
| Awaken | 1 group of buyer questions tracked in AI, at about half Anchor's pace | Emerging businesses with a lean team | 45-day outline guarantee | Strategic conversation, then a quote |
| Anchor | 2 groups of buyer questions (20 to 40 questions), covering the top 20% of the topics your buyers search, over 12 months | Established businesses | 45-day outline guarantee | Strategic conversation, then a quote |
| Ascend | 3 groups of buyer questions (40 to 80 questions), 3 new content pieces a month across platforms, covering over half the topics your buyers search | Growth businesses competing for category share | 45-day outline guarantee | Strategic conversation, then a quote |
| Attain | 5 groups of buyer questions (100 to 200 questions), 8 new content pieces a month across platforms, covering 95%+ of the topics your buyers search | Market leaders pursuing category saturation | 45-day outline guarantee | Strategic conversation, then a quote |
| Apex | Bespoke multi-brand, multi-market scope, managed end to end with dedicated resources | Enterprise and recurring-revenue (SaaS) businesses with several products, brands or markets | 45-day outline guarantee | Strategic conversation, then a quote |
Terms: the Ground Truth Guarantee also excludes the technical fix work. The 45-day outline guarantee on every monthly package covers the outline, not rankings or citations. Full terms
Every monthly package runs on one delivery system that plans, prioritises, ships and verifies the work each month, so each new page builds on the last. Without that rhythm, publishing turns ad hoc and results become hard to forecast. All five packages include:
| Area | What you get each month |
|---|---|
| Campaign governance | A delivery and sprint plan, a backlog ranked by buyer-question group, and managed change control, dependencies and stakeholder updates |
| Performance reporting | A report on what moved, what shipped and what is blocked, with next month's priorities and risks |
| Tracking and measurement | GA4 and Search Console health checks, agreed definitions for the conversions you count (leads, bookings, calls and enquiries), and a maintained dashboard with annotations and data-quality notes |
| Search and AI visibility monitoring | Indexing and crawl anomaly checks, branded and non-branded trend tracking, and spot checks of Google AI Overviews and other AI answers on your priority topics |
| Technical hygiene | A fix list of quick wins for your developers, covering redirects, canonical tags, broken links and internal links, with every fix verified and documented once it is live |
| Structured data and publishing quality | Validated schema on every new page, pre-publish checks of formatting, metadata, internal links, images and alt text, and consistency checks so every new page meets the same standard |
Aemorph's technical SEO is built for:
- Hospitals and healthcare providers whose service pages carry regulated claims.
- Financial services and insurance firms whose product pages need clean canonicals and redirects.
- B2B SaaS and technology vendors whose product pages need to read cleanly to every crawler.
- Professional services firms with deep practice-area pages.
- Higher education providers with multilingual course pages.
- High-ticket lifestyle and specialist services with large order values.
- High-ticket ecommerce with repeating product and category templates.
- Businesses at S$5M+ revenue that want the full LLM Influencer System.
It is not built for a platform without edit access to titles, canonicals, redirects, hreflang or structured data, or for a buyer who wants a one-off speed score.
Three Singapore agencies quoted Aemorph these monthly fees in June 2026, and Aemorph quotes each engagement after the strategic conversation.
| Provider | Offer | Monthly price | What the fee is tied to | Terms | Source date |
|---|---|---|---|---|---|
| D'Marketing Agency | Lite | S$900 | No guarantee | Not stated in the June 2026 quotes | Quoted Jun 2026 |
| Verz Design | SEO | S$1,200 | KPI targets only | Not stated in the June 2026 quotes | Quoted Jun 2026 |
| OOm | Boost | S$1,988 | 50% share of voice and 60% of keywords on page one | 12, 24 or 36 months; 60-day notice to exit | Quoted Jun 2026 |
| Aemorph | Five monthly packages, Awaken to Apex | Entry S$2,500 to S$7,500; enterprise from S$12,500 | The output you need, with buyer questions tracked across search and AI; every package carries the 45-day outline guarantee, and the Ground Truth Guarantee covers Sprint 1 bought on its own | Set out in your quote | Oct 2026 |
Source: agency quotes collected by Aemorph, June 2026.
How to choose the right technical SEO agency?
The right technical SEO agency diagnoses issues at the template and CMS level, specifies canonicals, redirects and hreflang, designs nested JSON-LD beyond basic organisation schema, separates AI search crawlers from AI training crawlers in robots.txt, and verifies every change your developers ship.
Canonicals, redirects and sitemaps then name one URL per page, and reciprocal hreflang connects your locale versions. Scope comes before any fix, and a strategic conversation scopes the technical work against these five tests.
Technical SEO Keeps Staging Sites Out of Google and Your Accounts in Your Name
Aemorph's technical SEO keeps your staging sites out of Google, so buyers land on your live pages, and leaves your domains, hosting, Search Console, GA4 and CRM in your ownership.
Every regulated claim is checked before it goes live, and your nominated point of contact signs it off before Aemorph publishes it.
A robots.txt file alone leaves a staging site exposed: a robots.txt rule does not keep a page out of Google, while noindex or password protection does, and the Robots Exclusion Protocol, the standard behind robots.txt, states that its rules are not a form of access authorisation. Aemorph specifies how your staging sites stay out of Google's index and verifies that they do.
Source: Google Search Central, robots.txt introduction, 2025; IETF, RFC 9309, 2022.
| Claim or data type | Where it applies | What Aemorph checks | Evidence standard | When |
|---|---|---|---|---|
| Client data and access | Every client | Client-owned assets, named least-privilege accounts, credentials in a password manager, staging blocked from indexing, ISO 27001-aligned practice | ISO 27001 alignment, not certification | From kick-off |
| Medical and health claims | Hospitals, clinics, dental, optometry | Conservative wording, no exaggerated promises | PubMed, professional associations, government health authorities | Before publication |
| Singapore healthcare advertising | Singapore medical and dental clients | Copy observes the Singapore healthcare advertising guidelines | The published guidelines | Before publication |
| Financial and insurance claims | Financial services, insurance | Disclaimers present, no guaranteed outcomes | Client point of contact sign-off | Before publication |
| Testimonials and before-and-after | Every regulated vertical | Used only where the law permits | Client point of contact sign-off | Before publication |
General guidance, not legal advice.
Technical SEO Puts Crawl and Index Blockers First in Your Programme
Fixing crawl and index blockers first means every page you publish afterwards reaches Google and the AI chats from the day it goes live, so your content work turns into rankings, traffic and the leads behind them.
Start with a free strategic conversation, or with the Showstopper Sensor bought on its own: if the AI chats still get your showstopper questions wrong 30 days after publishing, you get your Sprint 1 fee back.