Things are rarely as simple as the dashboard makes them look.

Observed symptoms.

Traffic drops.

Pages disappear.

Markets behave differently.

A migration goes live and something never quite comes back.

The tempting part is naming the problem quickly.

I'm more interested in what actually happened.

Search, systems & digital investigation.

See the work →

Concrete portal opening onto the sea, with a raking shadow across the wall.

Spatial crop

Temporary editorial placeholder.

01 / UNDER THE SURFACE

SURFACE /

Traffic drops.

UNDERNEATH /

The interesting part is rarely one element.

It's what happens between them.

A conceptual map of how a search symptom connects URLs, architecture, language, markets, internal links, data and technology.

URLs

Architecture

Language

Markets

Data

Technology

Search problems move through URLs, architecture, language, markets, internal links, data and technology. Looking at one piece in isolation can make a neat explanation. It does not always make the right one.

The problem rarely stays in its lane.

Search connects to websites, markets, users, content, data and technology. Following the problem sometimes means leaving the original label behind.

  1. Search
  2. Website
  3. Markets
  4. Users / Content
  5. Data
  6. Technology / Automation

02 / FOLLOW THE PROBLEM

I started in marketing. The problems kept getting more technical.

Search led to websites. Websites led to architecture, markets, data and automation. Lately, some of those questions lead to AI-mediated discovery.

I kept following them.

I'm Vera Rocha. I work across technical search, international websites and the systems around them.

Technical Growth & Search Systems

Curved concrete wall in raking light, with a dark shadow cutting diagonally across its surface.

Observational crop

Temporary editorial placeholder.

03 / WORK

What actually happened.

The finished answer is usually the least interesting part. These are problems I've worked through: what we knew at the beginning, what the evidence changed, what I did, what I could validate — and what remained uncertain.

Read the 30-second version →
Problem
Spain Internship moved to a new multilingual site. More than 2,000 historical URLs across six languages needed a defined destination.
Question
Which old URLs still mattered, and where should each one go, without redirect chains, loops or jumps between languages?
System
Historical URLs · localised slugs · redirects · sitemaps · vacancy records
Evidence status
Aug 2026

I diagnosed the URL problems in Spain Internship's multilingual migration, specified the redirect and URL architecture, and implemented it through AI-assisted development in Lovable. All 198 historical vacancy redirects in my specification appear exactly in the site's source code.

Source
My own August 2026 URL mapping workbooks and the site's source code (private).
Context
Growth Marketing Manager at The Student Mobility Group, working on Spain Internship.
Go underneath ↓
  1. THE SITUATIONPublic case facts are omitted until approved evidence exists.
  2. WHAT WE KNEWPublic case facts are omitted until approved evidence exists.
  3. THE FIRST THEORYPublic case facts are omitted until approved evidence exists.
  4. WHAT WE CHECKEDPublic case facts are omitted until approved evidence exists.
  5. WHAT DIDN'T EXPLAIN ITPublic case facts are omitted until approved evidence exists.
  6. WHAT CHANGED THE PICTUREPublic case facts are omitted until approved evidence exists.
  7. WHAT I DIDPublic case facts are omitted until approved evidence exists.
  8. HOW IT WAS VALIDATEDPublic case facts are omitted until approved evidence exists.
  9. WHAT THE EVIDENCE SUPPORTSPublic case facts are omitted until approved evidence exists.
  10. WHAT IT DOESN'T PROVEPublic case facts are omitted until approved evidence exists.
  11. WHAT I'D QUESTION NOWPublic case facts are omitted until approved evidence exists.

A CONCEPTUAL EXAMPLE

A site loses organic visibility after an international migration.

Hreflang is an obvious place to look.

Hreflang remains a plausible first look, then becomes one node among redirects, canonicals, internal links, sitemaps, URL structure and language relationships.

  • Hreflang
  • redirects
  • Canonicals
  • Internal links
  • Sitemaps
  • URL structure
  • Language relationships

The useful question isn't which box owns the problem.

It's how the pieces are behaving together.

This is a conceptual demonstration of the investigation model, not a historical case study.

Simple explanations can lead to expensive decisions.

I investigate what's actually happening before deciding what should change.

04 / SERVICES

You probably don't need to know what the service is called.

Tell me what's happening.

  • We migrated. Organic performance never really came back.

    Before changing more things, let's understand what changed.

  • We're operating across several markets and nobody fully trusts the international setup anymore.

    Let's separate localisation problems from search problems from architecture problems.

  • Search engines are indexing URLs we didn't expect them to find.

    That's usually a system question before it's a ranking question.

  • We're being asked about AI visibility, but we're not sure what is measurable yet.

    First: what can we actually observe?

Those problems may lead through technical SEO, international architecture, migrations, analytics, automation or emerging discovery systems. The route depends on what we find.

  • Technical SEO
  • International SEO
  • Search Migrations
  • Analytics & Automation
  • AI-mediated Discovery

Bring me the messy version →

05 / METHOD

A method for getting past the symptom.

  1. 01

    Diagnose

    Understand the real problem before prescribing the fix.

  2. 02

    Design

    Turn what we know into a clear plan across the system.

  3. 03

    Implement

    Make the change with enough detail that the strategy survives contact with the website.

  4. 04

    Validate

    Check what changed, what didn't and what the evidence supports next.

Diagnose → Design → Implement → Validate ↺

06 / FIELD NOTES

Things worth writing down before they become conclusions.

Observations, investigations and unresolved questions from search, websites and the systems around them.

Nothing published here yet.

  • OBSERVATION
  • INVESTIGATION
  • SYSTEM NOTE
  • EXPERIMENT
  • UNRESOLVED

07 / ABOUT

Vera Rocha, photographed in natural window light.

Human portrait

Temporary editorial placeholder.

I have a habit of following questions past the point where they stop belonging to my job description.

That's more or less how marketing turned into search, search into websites, and websites into technical systems, data and automation.

I like understanding how things connect. I like finding the point where the explanation stops making sense. And I like leaving a system easier to reason about than I found it.

HOW THE WORK CHANGED /

One question kept leading to another.

  1. 2021

    MSc Marketing

    University of Maia

  2. Oct 2021–Sep 2026

    The Student Mobility Group

  3. June 2022–June 2025

    Leadhackers

    SEO Specialist

  4. INTERNATIONAL WEBSITES

  5. WEB SYSTEMS / ARCHITECTURE

  6. ANALYTICS

  7. AUTOMATION

  8. UNDERNEATH /

    Technical Growth & Search Systems

    Search, systems & digital investigation.

RECRUITING?

If you're here for the 30-second version, I made one.

Identity
Vera Rocha
Technical Growth & Search Systems
Territory
Search, systems & digital investigation.
Location
Portugal → working internationally.

Capabilities

  • Technical SEO
  • International SEO
  • Search Migrations
  • Analytics & Automation
  • AI-mediated Discovery

Bring me a problem.

The messy version is fine.

You don't need to diagnose it before you contact me.

It can start with search, a website, a brand, a market, a number that doesn't make sense — or something harder to name.

LinkedIn ↗

01 / Your name

02 / Your email

03 / What's happening?

What changed? What are you seeing? What have you already tried?

04 / What might this touch?

Optional. Don't worry if you're not sure.

I use this only to answer you. It isn’t added to a list or used for anything else.