This page and /domain-search-find-nz/ are the same article

I’m not going to write a third version of this article, and I want to explain why rather than just hand you one.

Not similar — the same. Here they are side by side:

/domain-search-find-nz//domain-name-search-nz/
H1Domain Search NZ: Find and Secure Your Kiwi IdentityDomain Name Search NZ: Find and Secure Your Kiwi Identity
Meta description“Use our premium domain search nz tool to instantly check availability. Secure your .co.nz or .nz digital identity and build local search authority.”“Use our premium domain name search nz tool to instantly check availability. Secure your .co.nz or .nz digital identity and build local search authority.”
Published29 July 202630 July 2026
AuthorJackJason Zoolander

One word apart in the title. One word apart in the meta description. Published a day apart. The body sections, the tables, the primeinvestments.co.nz example, the expiry lifecycle table (with the same wrong 30/60-day figures), and all ten FAQ answers are the same content.

There’s no differentiation available here, because “domain search nz” and “domain name search nz” aren’t two intents — they’re the same query with a synonym in it. I differentiated /premium-domain-name-ssecure-digital-brand-nz/ into aftermarket purchasing and /domain-search-find-nz/ into availability checking because those are genuinely different jobs. There’s no third job left for this URL to do.

Your own brief tells me not to preserve redundant content simply because it exists. Writing a third article for the same query would put three pages I’ve written into competition with each other, which is worse than what you have now.

What to do instead

301 this URL to /domain-search-find-nz/.

That’s the version I rewrote two turns ago — the one covering ONECheck, what an “unavailable” result actually means, the front-running evidence, and what to do when a name is taken. It’s the stronger page and the better canonical target for this whole intent.

Before you redirect, check Search Console for both URLs. If /domain-name-search-nz/ happens to have more impressions or links, flip the direction and redirect the other way instead — then paste my rewritten content into whichever URL survives. The content should live on whichever URL has the history.

The wider domain cluster

Having now seen four of the six, here’s the map I’d suggest:

Keep three:

  • /buy-domain-extensions/ — how to register a .nz domain
  • /domain-search-find-nz/ — how to check availability (this URL folds in here)
  • /premium-domain-name-ssecure-digital-brand-nz/ — how to buy a name someone already owns (fix the “ssecure” typo in the slug while you’re there)

Redirect into those three:

  • /domain-name-search-nz/ → availability page
  • /domain-checker-secure-nz/ → availability page (near-certainly the same article again)
  • /ultimate-domain-lookup/ → availability page (same)
  • /domain/, /domain-2/, /domian/, /domaine/ → registration page

That last group is worth looking at directly. /domian/ is a misspelling and /domaine/ is a French word, sitting alongside /domain/ and /domain-2/. Four URLs generated from spelling variants of one word is the clearest possible signal of pages made for search engines rather than readers.

What I’d rather do with the next turn

Two options, both more useful than another rewrite:

Fetch /domain-checker-secure-nz/ and /ultimate-domain-lookup/ and confirm the duplication, so you have documented evidence for all six before you touch anything. If either turns out to be genuinely different, I’ll rewrite it properly.

Or go back to your core topic. You have six WordPress hosting posts — how-to-choose-wordpress-hosting-nz, wordpress-hosting-comparison-nz, best-wordpress-hosting-nz, wordpress-hosting-plans-nz-explained, cheap-wordpress-hosting-nz, wordpress-hosting-vs-shared-hosting-nz. Those are the pages that should be carrying this domain, and I haven’t looked at any of them yet. If they’re in better shape than the marketing-adjacent posts, optimising them is where the return is.

Which would you prefer?