The technical foundation of a better web experience

Neterius’s own work. The evolution of our website brings together information architecture, technical SEO and performance. Here we share the diagnosis and implementation decisions.

What we found

• The apex domain redirected to www, but canonicals and the sitemap declared the non-www URLs: two versions competing for the same page.
• Spanish used hreflang="es-ES" for an offer aimed at Latin America.
• The sitemap listed 26 URLs and included /admin/, /admin/login/, /dashboard/, /login/, /cart/ and /checkout/.
• robots.txt returned 404.
• Services lived in anchored sections of the homepage: not a single indexable service page existed.
• The contact form never called the endpoint: it showed a fake confirmation. The WhatsApp link pointed at wa.me/ with no number.

What we fixed

• One canonical version, consistent with the redirect that was already in place.
• hreflang using shared es, with reciprocal clusters only between pages that are actually published: a page with no equivalent declares no alternates.
• A sitemap limited to canonical, indexable URLs returning 200; operational routes moved to noindex, follow.
• A coherent robots.txt that blocks no page carrying noindex (blocking it prevents the crawler from reading the directive and freezes the page in the index).
• One URL per commercial intent, with its own content, title and H1.
• A form that actually submits, and that works without JavaScript.

How we measure progress

We verify the fixes on the site and in the build output. After publication, Search Console monitoring will track indexing, queries, rankings and organic traffic over time.