Skip to content
Yassir Halaoui
FR
Lire en français

Services

Technical SEO, written into the code

Most SEO problems on modern web apps are engineering problems: pages that render late, duplicate URLs, hreflang that points one way, structured data that won't validate. I fix them in the code.

In short

Yassir Halaoui does technical SEO as engineering work: server rendering, structured data, multilingual hreflang, canonical URLs, crawl budget, Core Web Vitals and visibility in AI answer engines, implemented in the codebase. RevealTogether, which he built, ranks on Google's first page in English and Spanish for its core searches, and this site reached the first page for his name within six weeks of the domain being registered.

RevealTogether, in English and Spanish
Page one
See the project
Articles published in three languages
350+
New domain to page one for my name
6 weeks

How I work

What I fix

Pages that only exist after JavaScript runs. Ten URLs for one page. Hreflang that points one way, so Google ignores all of it. Canonicals that redirect. Structured data with untyped references, which is the error Search Console flagged on this very site and which I fixed the same day. Sitemaps full of redirects. Layout shift that wrecks Core Web Vitals.

None of that needs a plugin. It needs someone who reads the rendered HTML, finds the line of code responsible and changes it without breaking the product.

Built for answer engines too

People ask ChatGPT, Perplexity and Google's AI answers before they ever click. I structure pages so a model can quote them: a direct answer near the top, real numbers, entities linked in JSON-LD, an llms.txt file, and crawlers such as GPTBot and ClaudeBot let in and served complete metadata.

Multilingual without the usual mess

RevealTogether runs in English, French and Spanish, and this site in English and French. Sub-path locales, two-way hreflang with an x-default, canonicals per language, and a single function that builds every absolute URL. Retrofitting that after launch costs weeks. Doing it first costs a day.

Content architecture

Long-tail rankings come from depth on a few topics, not from one page per keyword. I've also done the opposite job: removing a cluster of thin doorway pages that was dragging a whole domain down. Hubs, clusters and internal links written so a person would actually want to follow them.

How we start

  1. 01

    An audit of the rendered HTML, not the source code.

  2. 02

    A ranked list of fixes, each with its expected impact.

  3. 03

    The fixes, in your codebase, reviewed like any other change.

  4. 04

    Search Console checks until the reports agree.

Write to me · consultingyassir@gmail.com

Stack

Rendering
  • Next.js App Router
  • React Server Components
  • Static generation
  • i18n routing
Search signals
  • JSON-LD and schema.org
  • hreflang
  • Canonicals
  • Image and video sitemaps
  • robots.txt
  • IndexNow
  • llms.txt
Measurement
  • Google Search Console
  • Bing Webmaster Tools
  • Core Web Vitals
  • Privacy-first analytics

Questions

Can a developer do SEO, or do we need an agency?

For technical SEO a developer is usually the faster route, because the fixes live in the code. An agency can tell you that hreflang is broken. Someone who can open the codebase fixes it the same afternoon.

How do you do SEO in Next.js?

Render on the server or at build time, use the Metadata API for titles, canonicals and Open Graph, generate the sitemap and robots.txt from the same content as the pages, add JSON-LD, and keep every route static unless it can't be. One detail that catches people out: a page's alternates replace the layout's instead of merging with them.

How do you get a website cited by ChatGPT or Perplexity?

Let their crawlers in, serve them complete HTML, and write pages a model can quote: a direct answer near the top, real figures, clear entities in structured data, and an llms.txt file summarising the site. Then earn mentions on other sites, which matters as much for AI answers as it does for Google.

How long does it take a new website to rank?

For your own name, weeks. This domain reached Google's first page for my name about six weeks after it was registered. For competitive topics it's months, and it depends on content and links more than on code.

Do you handle multilingual SEO and hreflang?

Yes. RevealTogether is in three languages and this site in two, both with two-way hreflang, an x-default and per-language canonicals generated from a single source.

Which Search Console errors can you fix?

Structured-data errors such as invalid object types, redirect and canonical problems, pages discovered but not indexed, duplicate URLs, broken hreflang and Core Web Vitals regressions. The first step is always reading what Google actually received.

Shipped work

Competences behind it

Field notes

Also on offer

Every competence