AGLX Technical SEO Fixes | Fabric Digital

The short version

The NZ section has good foundations: the copy is written for NZ, the language and most hreflang tags are set up correctly, and the site is secure. What holds it back is how it is connected to the rest of the site and how fast it loads. Nothing on the site links to the NZ homepage, NZ visitors are sent to US pages by the footer and logo, three NZ pages are missing hreflang tags, old NZ URLs still return errors, the business details in the schema do not match the Google Business Profile, and the NZ homepage takes over 30 seconds to show its main image on a phone.

All six fixes are straightforward for a WordPress developer. Fixes 1 to 5 are quick changes; fix 6 (speed) is the biggest piece of work and has the most effect on every page.

9live NZ pages checked

0normal links to the NZ homepage

32/100NZ homepage mobile speed

117.7 MBof images across the site

The six fixes

Click any fix to jump to the steps. Tick steps off as they are done; progress saves in this browser.

1🏠Give the NZ homepage links from the rest of the site0 normal links to the NZ homepageDeveloper · Quick 2🧭Keep NZ visitors on NZ pages9 US service links in the NZ footerDeveloper · Quick 3🌐Complete the hreflang tags3 NZ pages with no hreflang tagsDeveloper · Quick 4↪Redirect old NZ URLs that still get visits5 old or planned NZ URLs returning 404Developer · Quick 5📍Match the business details in schema to the Google Business Profile1022 postcode in schema (Google says 1010)Developer · Quick 6⚡Speed up the site, starting with images32/100 NZ homepage mobile speed scoreDeveloper · Project

Removed from the report

Fix1

NZ section

Give the NZ homepage links from the rest of the site

DeveloperEffort: 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.

What to do

On every /nz/ page, point the logo to https://www.aglx.com/nz/ instead of the US homepage.
Add a small region switch ("United States | New Zealand") to the header and footer of every page, linking to the matching page in the other region where one exists.
Add an "AGLX Asia Pacific" block to the US homepage linking to /nz/.
Add a "Home" item to the NZ menu that links to /nz/.

Examples

Where	Links to now	Should link to
Logo on all 9 NZ pages	https://www.aglx.com (US homepage)	https://www.aglx.com/nz/
US homepage	No link to /nz/	"AGLX Asia Pacific" block linking to /nz/
NZ main menu	8 NZ service pages	Add the NZ homepage

▦Full list in the data sheetNZ internal links tab→

Removed from the report

Fix2

NZ section

Keep NZ visitors on NZ pages

DeveloperEffort: Quick

9US service links in the NZ footer

What we found

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.

What to do

Create a separate footer menu for the /nz/ pages that links to the NZ service pages. Use the NZ menu in Elementor's footer template with a display condition for /nz/ pages.
Build /nz/contact-us/ (or stop the redirect and point it at the Asia Pacific booking page until it exists).
Change the six "Learn more" buttons on the NZ homepage to descriptive text, for example "Explore adaptive strategy" and "See the Flow Learning Lab".
Check the body copy of each NZ page for any remaining links to US pages and swap them for the NZ version.

Examples

NZ page	Footer link	Should go to
All 9 NZ pages	/adaptive-strategy/	/nz/adaptive-strategy/
All 9 NZ pages	/adaptive-leadership-training/	/nz/adaptive-leadership/
All 9 NZ pages	/flow-lab/	/nz/flow-learning-lab/
All 9 NZ pages	/ice-innovation-framework/	/nz/ice-innovation/
All 9 NZ pages	/team-organizational-coaching/, /peak-performance-teaming-workshops/, /no-way-out/	The NZ versions once built, or remove from the NZ footer

▦Full list in the data sheetNZ internal links tab→

Removed from the report

Fix3

NZ section

Complete the hreflang tags

DeveloperEffort: Quick

3NZ pages with no hreflang tags

What we found

Six NZ pages have correct, two way hreflang tags with their US twins, which is good. Three do not: /nz/the-flow-system/ (its US twin /the-flow-system/ has none either), and the two NZ only pages, /nz/integrated-risk-management/ and /nz/complexity-informed-practitioners/.

Why it matters

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

Add the tags below to both Flow System pages.
Add a self referencing en-nz tag to the two NZ only pages.
When the NZ Team Coaching and Peak Performance pages go live, add hreflang pairs to them and their US versions.
Re-check with the Hreflang tab in the sheet.

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/" />

▦Full list in the data sheetHreflang tab→

Removed from the report

Fix4

NZ section

Redirect old NZ URLs that still get visits

DeveloperEffort: Quick

5old or planned NZ URLs returning 404

What we found

Earlier versions of the NZ section used different URLs. These now return a 404 error but still get visits in GA4: /nz/resources/complexity-informed-practiotioners/, /nz/resources/the-flow-system/, /nz/resources/ and /nz/the-flow-lab/. The planned /nz/team-organisational-coaching/ also returns 404, and /nz/peak-performance-teaming-workshops/ redirects to the US page.

Why it matters

Every visit to a 404 page is a lost lead, and any link pointing at these URLs passes nothing to the site.

What to do

Add the 301 redirects listed in the Redirect map tab (Yoast Premium Redirects, the Redirection plugin, or Cloudflare redirect rules).
Test each one returns a single 301 to a live page.
When the NZ Team Coaching and Peak Performance pages are published, change their temporary redirects to point at the new pages.

Examples

Redirect from	To
/nz/resources/complexity-informed-practiotioners/	/nz/complexity-informed-practitioners/
/nz/resources/the-flow-system/	/nz/the-flow-system/
/nz/the-flow-lab/	/nz/flow-learning-lab/

▦Full list in the data sheetRedirect map tab→

Removed from the report

Fix5

NZ section

Match the business details in schema to the Google Business Profile

DeveloperEffort: 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.

What to do

Replace the NZ Organization schema with the ProfessionalService block below (sitewide on /nz/ pages).
Add a Service block to each NZ service page (example below for Adaptive Strategy).
Add the phone number to the NZ header or footer, matching the Google profile exactly.
Test each page in Google's Rich Results Test.

Ready to use code

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "ProfessionalService",
  "@id": "https://www.aglx.com/nz/#business",
  "name": "AGLX Asia Pacific",
  "url": "https://www.aglx.com/nz/",
  "telephone": "+64 210 327 300",
  "email": "info@aglx.com",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "12 Madden Street",
    "addressLocality": "Auckland CBD",
    "addressRegion": "Auckland",
    "postalCode": "1010",
    "addressCountry": "NZ"
  },
  "areaServed": { "@type": "Country", "name": "New Zealand" },
  "parentOrganization": { "@type": "Organization", "name": "AGLX", "url": "https://www.aglx.com/" },
  "sameAs": ["https://www.linkedin.com/company/aglx-consulting-llc/"]
}
</script>

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Service",
  "name": "Adaptive Strategy Consulting",
  "serviceType": "Strategy consulting",
  "url": "https://www.aglx.com/nz/adaptive-strategy/",
  "provider": { "@id": "https://www.aglx.com/nz/#business" },
  "areaServed": { "@type": "Country", "name": "New Zealand" }
}
</script>

▦Full list in the data sheetSchema tab→

Removed from the report

Fix6

Whole site, including NZ

Speed up the site, starting with images

DeveloperEffort: 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.

What to do

Compress and resize the images in the Large images tab, starting with the largest (Santa_2023_Page_4.png is 9 MB, the Brian Rivera photo on the homepage 4.3 MB). Target under 200 KB each.
Turn on WebP conversion and lazy loading site wide (Breeze is already installed; add ShortPixel, Imagify or Cloudflare Polish for WebP).
Load reCAPTCHA only on pages with a form.
Turn on Elementor's performance features: Improved CSS Loading, Inline Font Icons, Lazy Load Background Images.
Remove Smart Slider 3 assets from pages that do not use a slider, and load Google Fonts once (Roboto is loaded from Google and locally).
Delay the HubSpot (5 scripts), Clarity and gtag scripts until the visitor interacts, using Breeze or Perfmatters.
Re-run Lighthouse and aim for 70 plus on mobile.

Examples

Page (mobile)	Score	Largest paint	Page weight
NZ homepage	32	35.2 s	11.7 MB
NZ Adaptive Strategy	39	8.5 s	1.9 MB
NZ Flow Learning Lab	41	7.2 s	2.1 MB
US homepage	31	39.4 s	13.9 MB
Blog article	50	4.5 s	1.5 MB
Case study	49	4.5 s	2.0 MB

▦Full list in the data sheetLarge images tab→

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

How we checked

We crawled every URL in the site's 11 XML sitemaps and followed every internal link (172 URLs), checked all 369 images, ran Lighthouse on six page types on mobile and the NZ homepage on desktop, validated every hreflang tag and structured data block, compared the NZ copy against the US pages, and reviewed GA4 and the Google Business Profile.

Data sheet tabs

Action list NZ internal links Hreflang Redirect map Schema Speed tests Large images