Fabric Digital · AGLX Technical SEO AuditData sheet
Technical SEO Audit
aglx.com, with a focus on the NZ section
Prepared for AGLX Asia Pacific by Fabric Digital · 22 October 2026
NZ homepage speed (mobile)
NZ homepage speed (desktop)
Lighthouse SEO
Accessibility
Best practices
The short version
The NZ section is in good shape where it counts most: the copy is genuinely unique to NZ, the language and hreflang are set up correctly on most pages, and the site is secure and cached. What is holding it back is how it is connected and how fast it loads. Nothing on the site links to the NZ homepage, NZ visitors are routed to US pages and to the North America booking page, and the NZ homepage takes over 30 seconds to show its main image on a phone. Across the whole site we found broken and redirecting links, duplicate URLs, pages nothing links to, and thin archive pages open to Google.
The good news is that most of this is quick, low cost work. The Fix first items below can be done in a few days and remove the biggest barriers. Long lists (every URL, title and image) are in the linked Google Sheet, so this report stays readable.
172URLs crawled, 160 of them indexable
9live NZ pages
32/100NZ homepage mobile speed
8broken internal links
27pages with no internal links
117.7 MBof images across 369 files
What is already working
HTTPS everywhere, with Cloudflare caching pages at the edge
Every page has a canonical tag, and none point to the wrong place
All structured data on the site is valid (0 errors)
The NZ copy is genuinely different from the US pages (0 to 1% overlap on service pages)
Hreflang is correct and two way on the 6 NZ pages that have it
NZ pages declare en-NZ as their language, the US pages en-US
robots.txt is clean and the XML sitemaps are in place
Every page is mobile friendly and has Open Graph images for sharing
GA4 is installed on every page
Action plan at a glance
Work top to bottom. Fix first items have the biggest effect for the least effort. Tick the steps in each section as they are done; progress is saved in this browser.
Give the NZ homepage links from the rest of the site
Fix firstDeveloperEffort: Quick
0normal links to the NZ homepage
What we found
Nothing on aglx.com links to /nz/ with a normal link. The logo on every NZ page goes to the US homepage, the US homepage only mentions the NZ section in a hidden hreflang tag, and the NZ menu lists the NZ service pages but not the NZ homepage itself.
Why it matters
Google finds pages and judges their importance through internal links. The NZ homepage is the page we want ranking for broad NZ searches, yet as far as the site structure is concerned it is an island. It is still the top NZ landing page in GA4 (159 sessions in 90 days), mostly from direct and email visits.
Every NZ page has a footer "Services" list with 9 links to the US service pages, so each NZ page links to the US versions more often than to its own. /nz/contact-us/ redirects to the US contact page, and the six "Learn more" buttons on the NZ homepage all use the same anchor text.
Why it matters
Internal links tell Google which pages matter for which market. At the moment the NZ section is passing its own authority to the US pages, and NZ buyers who click around end up reading US copy, US case studies and a US contact page.
The NZ versions once built, or remove from the NZ footer
NZ 3
Send every NZ booking button to the Asia Pacific team
Fix firstDeveloperEffort: Quick
3NZ pages booking calls with the North America team
What we found
The NZ homepage, Complexity and Flow System pages link "Book a call" to /book-a-call/na/, which is the North America booking page (and a duplicate URL of /book-a-call-na/). Six other NZ pages use Steve's HubSpot calendar. Every NZ page also has at least one button that links to "#" and does nothing (two on the NZ homepage). The Asia Pacific booking page, /book-a-call-asia-pacific/, has no internal links at all.
Why it matters
Booking a call is the main conversion on the site. NZ buyers are being sent to the US team or to a dead button at the exact moment they are ready to talk.
What to do
Examples
NZ page
Booking link now
/nz/
/book-a-call/na/ (North America) + 2 "#" buttons
/nz/complexity-informed-practitioners/
/book-a-call/na/ (North America) + 1 "#" button
/nz/the-flow-system/
/book-a-call/na/ (North America) + 1 "#" button
6 other NZ pages
meetings.hubspot.com/steven-mccrone + 1 "#" button each
Without hreflang Google can show the US Flow System page to NZ searchers, or treat the two pages as near duplicates and pick one. The NZ only pages need a self reference so they are clearly marked as en-NZ.
What to do
Ready to use code
<!-- On https://www.aglx.com/nz/the-flow-system/ AND https://www.aglx.com/the-flow-system/ -->
<link rel="alternate" hreflang="en-us" href="https://www.aglx.com/the-flow-system/" />
<link rel="alternate" hreflang="en-nz" href="https://www.aglx.com/nz/the-flow-system/" />
<link rel="alternate" hreflang="x-default" href="https://www.aglx.com/the-flow-system/" />
<!-- On the NZ only pages (no US version) -->
<link rel="alternate" hreflang="en-nz" href="https://www.aglx.com/nz/integrated-risk-management/" />
<link rel="alternate" hreflang="en-nz" href="https://www.aglx.com/nz/complexity-informed-practitioners/" />
Match the business details in schema to the Google Business Profile
NextDeveloperEffort: Quick
1022postcode in schema (Google says 1010)
What we found
The NZ pages carry Organization schema named "AGLX, LLC" with Auckland and postcode 1022, but no street address or phone. The Google Business Profile lists AGLX at 12 Madden Street, Auckland CBD 1010, phone 0210 327 300. There is no phone number anywhere in the NZ section, and none of the NZ service pages have Service schema.
Why it matters
Consistent name, address and phone across the site, schema and Google Business Profile is a core local ranking signal. Service schema tells Google exactly what each NZ page offers and where.
Only one NZ title (Adaptive Leadership) includes NZ, the NZ homepage title has no NZ or Auckland in it, and 6 of 9 NZ titles run past the 60 characters Google shows. Three H1s say nothing about the service: "Better Performance Through Adaptability", "Science-based Answers to Build Flow" and "AGLX as Complexity-Informed Practitioners".
Why it matters
The title and H1 are still the strongest on page signals, and the title is the headline people see in Google. Adding NZ tells both Google and the searcher this is the local version.
What to do
Examples
Page
Current title
Suggested title
/nz/
Executive Coaching, Business Strategy & Consulting | AGLX
Business Strategy & Executive Coaching NZ | AGLX
/nz/adaptive-strategy/
Adaptive Strategy & Strategic Consultants | AGLX Asia Pacific
Adaptive Strategy Consultants NZ | AGLX
/nz/the-flow-system/
Distributed Leadership & The Flow System | AGLX
The Flow System NZ | Distributed Leadership | AGLX
86 of the 108 images on the NZ pages (60 unique files) have empty alt text, including every client logo on the NZ homepage. Most photos have generic file names such as aglx2.jpg and ll1.jpg. The /nz/integrated-risk-management/ page shows a US "Service Disabled Veteran Owned" certification badge.
Why it matters
Alt text is how Google understands images and it adds relevant words to the page. Client logos with alt text ("Watercare logo", "NZ Super Fund logo") also reinforce the NZ client list. The US badge means nothing to NZ buyers.
Technical issues that affect every page, including the NZ section
Site 1
Speed up the site, starting with images
Fix firstDeveloperEffort: Project
32/100NZ homepage mobile speed score
What we found
Lighthouse mobile performance scores range from 31 to 50 across the six page types we tested. The NZ homepage scores 32 with a 35 second largest paint and an 11.7 MB page; the US homepage scores 31 at 13.9 MB. Across the site there are 117.7 MB of images in 369 files: 111 are over 200 KB, 18 are over 1 MB, and only 16 use a modern format such as WebP. 580 images load straight away instead of lazily, and reCAPTCHA (346 KB) loads on all 160 pages even though only a few have a form.
Why it matters
Page speed and Core Web Vitals are ranking factors, and most visitors are on phones. On a page that takes over 30 seconds to show its main image on a mobile connection, many people leave before they see anything.
Eight internal links point to pages that no longer exist (404). Most are in older articles and facilitation technique pages that link to old URLs, and one dead URL is listed in the video sitemap.
Why it matters
Broken links waste the visitor's click and the value the link would pass, and a pattern of them tells Google the site is not well maintained.
The main menu links to /aglx-thinking and /case-studies without the trailing slash, so on all 142 pages that use the menu, both links go through a 301 redirect. Ten other internal links do the same.
Why it matters
Each redirect adds a delay for visitors and wastes crawl time. Google prefers internal links to point straight at the final URL.
Twelve pages exist at two addresses. The facilitation techniques are live at both /facilitation-technique-pre-mortem/ and /methods/pre-mortem/ (and similar /techniques/ URLs), and the booking pages at both /book-a-call-na/ and /book-a-call/na/. The duplicates point their canonical tag at the main version, which helps, but other pages link to the duplicates. Steve McCrone also has two profile pages: /steve-mccrone/ and /team-member/steven-mccrone/.
Why it matters
Duplicates split link value and crawl time. A canonical tag is a hint; a 301 redirect is a clear instruction.
27 pages in the sitemaps have no internal links pointing to them. They include the NZ homepage, the Asia Pacific booking page, all 14 facilitation technique pages, the Energy sector page, the Peak Performance Safety Training page and Steve McCrone's profile.
Why it matters
Pages with no internal links are hard for Google to find and rank, and visitors can only reach them from search or ads. The facilitation technique pages are some of the best free content on the site and they are stranded.
Keep thin archive pages and site search out of Google
NextDeveloperEffort: Quick
33archive pages open to Google
What we found
21 blog tag pages, 8 author pages, 3 region pages and 1 category page are in the sitemaps and open to indexing. They are thin lists of posts with near identical titles (nine are titled "AGLX | Thinking Blog") and the same H1, "AGLX Thinking". Internal search results such as /?s=strategy can also be indexed, and the video sitemap lists one URL that is a 404.
Why it matters
Dozens of thin, repetitive pages dilute the site's quality signals and compete with the real articles and service pages.
Fill the gaps in titles, meta descriptions and H1s
NextContent writerEffort: Half day
24pages with no H1
What we found
19 pages have no meta description (10 of them team member pages), 11 pages share a title with another page, 10 share a meta description, and 24 pages have no H1 heading (11 team member pages and 8 landing pages). 54 titles are under 30 characters, for example "AGLX | Energy Sector".
Why it matters
Missing or repeated titles and descriptions make Google write its own snippet, usually a worse one. Pages without an H1 give Google a weaker signal about the main topic.
Every page has valid basic schema from Yoast (WebPage, Breadcrumb, Organization) and none of it has errors. But only 1 of 55 blog articles is marked up as a BlogPosting, case studies have no Article markup, team members have no Person markup, and no page anywhere has Service markup.
Why it matters
Rich structured data helps Google and AI search tools understand who wrote what, what AGLX sells, and who the experts are, which matters a lot for a consultancy built on its people.
10 links to other websites are dead (404, or the site is no longer reachable). Three on the /facilitation-technique-alternative-futures/ page are typing mistakes that turned internal links into broken external ones (http://methods/think-write-share). One article embeds a LinkedIn image link that has expired.
Why it matters
Dead outbound links make articles look neglected and send visitors nowhere.
The site runs on HTTPS behind Cloudflare and pages are cached well. But it sends none of the standard security headers (HSTS, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy), and http://aglx.com/ takes two redirects to reach https://www.aglx.com/.
Why it matters
Security headers are a trust and best practice signal (Lighthouse best practices scores are 69 to 73), and HSTS makes sure browsers always use HTTPS. One clean redirect is faster than two.
What to do
Ready to use code
Cloudflare dashboard > SSL/TLS > Edge Certificates:
Always Use HTTPS: On
HTTP Strict Transport Security (HSTS): Enable, max-age 6 months, include subdomains, no preload to start
Cloudflare > Rules > Transform Rules > Modify Response Header (all requests):
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
Referrer-Policy: strict-origin-when-cross-origin
Permissions-Policy: camera=(), microphone=(), geolocation=()
Site 11
Fix the accessibility issues Google can see
When time allowsDeveloperEffort: Half day
1,693links that go to "#"
What we found
Every page has template links that go to "#" (1,693 in total). Lighthouse flags "Learn more" links with no descriptive text, headings that skip levels, blog and case study pages with no main landmark, buttons with no accessible name, small touch targets, and low colour contrast on case studies, where the layout also shifts while loading (CLS 0.121).
Why it matters
Accessibility and SEO overlap: descriptive links, a clear heading order and a stable layout help Google understand the page and help every visitor use it.
What to do
Site 12
Set up tracking so results can be measured
Fix firstAGLX teamEffort: Quick
0GA4 key events
What we found
GA4 is installed on every page, which is good, but no key events are set up, so the 23 form submissions in the last 90 days were not counted as leads. A large share of sessions come from Germany (1,754 against 546 from NZ), most likely bots and tools. We cannot see Search Console data for aglx.com, and the Semrush site audit for the site last ran on 30 March, before the NZ section existed.
Why it matters
Without key events and Search Console, there is no reliable way to show which pages and searches produce enquiries, or to spot indexing problems early.
What to do
How we checked
We crawled every URL in the site's 11 XML sitemaps and followed every internal link (172 URLs), then checked all 369 images and 132 outbound links. We ran Lighthouse on six page types on mobile and the NZ homepage on desktop, checked server headers and redirects, validated every hreflang and structured data block, and compared the NZ copy against the US pages. We also reviewed GA4 (last 90 days), the Google Business Profile and Semrush. Search Console was not available to us.