Skip to content

Strategy and personal execution

Technical SEO Consulting and Implementation

Led growth at cnvrg.io before its acquisition by Intel.

A page can return 200 and still be hard to discover, render or index. I find the technical constraint, prioritize it against the business impact and personally implement the agreed work. You get a record of what changed and how it was checked.

When technical SEO is the right next step

Three ascending sculptural metal forms have finely illuminated teal edges.

Use this service when important pages are excluded from search, a JavaScript site hides useful content, a migration has changed URLs or templates, or international versions compete with each other. Start with the pages that support real buying decisions, rather than a score covering every minor warning.

I work as a Fractional CMO & Head of Growth: I connect technical search work to acquisition, conversion and the revenue funnel. An audit can stand alone; an implementation engagement includes the fixes we agree I will own, with your developers involved where access or infrastructure requires them.

What the work can cover

Crawling and indexing

Review response codes, robots directives, canonicals, sitemaps and internal discovery. Identify which URLs should be indexed and which exclusions are intentional.

Rendering and templates

Compare delivered HTML and rendered content, navigation, metadata and links. Locate template defects that affect many pages; distinguish a rendering issue from a content or demand problem. To compare delivered HTML evidence with rendering assumptions, see JavaScript SEO and HTML evidence checker.

Architecture and international SEO

Review page hierarchy, internal links, pagination, language alternatives and canonical relationships. Keep Hebrew and English versions useful and mutually discoverable.

Migration and performance

Map old and new URLs, test redirects and critical templates, and review Core Web Vitals evidence. A performance task names the affected experience and a measurable acceptance check.

How we work

1

Record the baseline

Agree priority URLs, target markets and the business question. Use available Search Console exports, site crawls, CMS access and relevant logs. Record unavailable inputs explicitly.

2

Fix by impact and dependency

Deliver a prioritized issue register with evidence, affected templates, suggested changes, owner and acceptance test. I implement the agreed content, configuration and site work; infrastructure changes get a named developer owner.

3

Verify the release

Compare the same URLs before and after the change. Recheck rendered content, status, canonical, indexability, internal links and language signals. Keep a rollback reference for material site changes.

4

Review what search actually did

Check later indexing and search observations separately from release checks. Traffic, qualified inquiries and revenue require their own data and an appropriate observation window.

What you receive

A reproducible baseline, a prioritized technical backlog and an implementation record for the agreed scope. Each material issue includes a location, evidence, owner and a pass/fail acceptance check. The handover separates resolved defects from items awaiting search-engine processing.

Illustrative example: if a Hebrew service page points its canonical to an unrelated English page, the fix must reconcile the canonical and language alternatives, then verify both versions. A correct release check proves the tags and responses changed; it does not prove Google has reindexed the page or improved its position.

Relevant experience, with the right attribution

My published case studies cover my work at Elementor, at Riverside as Head of Paid Acquisition and at cnvrg.io as Head of Growth. They explain the wider operating context. They are not presented as measured results from this technical SEO service or as a promise of your future performance.

Questions about the service

Do you implement fixes or only deliver an audit?

Both are available. I personally execute the work included in the implementation scope. Developer-dependent changes have a named owner and verification plan.

Can you work on a JavaScript or Next.js website?

Yes. The review compares the HTML search engines receive with rendered pages and checks routes, metadata, links and assets. The implementation scope depends on the stack and access available.

Does a migration need a separate plan?

Yes. URL mapping, redirect rules, template checks and rollback are agreed before release. Existing search traffic is a baseline to preserve, not a reason to skip verification.

Do you cover Hebrew and English?

Yes. The scope can include both languages, their page relationships and hreflang. Translation quality and a useful local offer matter alongside technical tags.

What does success mean?

First, the agreed defect is resolved and independently checkable. Then we observe indexing, search demand, qualified inquiries and business outcomes using their own evidence.

How are fees and timing agreed?

After reviewing scope, access and dependencies. Contract terms, including duration and notice period, are agreed per engagement. No fixed price or completion date is implied here.

When an assistant finds the button but cannot finish the task

A site can be readable in search while a person or AI assistant still struggles to download the right document, understand an offer or recover from an error. Start with one useful buyer task and inspect what actually happens.

I define the input and expected result, inspect the content the browser receives and implement the agreed structural, link and recovery changes. Any additional content format or agent interface must preserve the same facts, permissions and normal website experience.

Define a task, check reading and action, fix the obstacle and verify the result.
  1. Define the task
  2. Check reading and action
  3. Fix the obstacle
  4. Verify the result

What the team retains

  • A task and expected result, including allowed actions and actions requiring separate approval.
  • Checks of actual information, links or files and recovery after invalid input.
  • A version-bound change record and repeatable acceptance test.

Illustrative example: a presentation link works but downloads an outdated file. Fix the file and its description, then inspect the download. A compatibility score would not resolve that content error.

Measure the named task: correct information and file, recovery and an authorized result. Keep untested tasks separate from observed failures. Compatibility does not establish citation, ranking or conversion outcomes.

Frequently updated content needs repeatable publication acceptance

On a frequently updated site, a visibility question can begin with publishing itself. Before changing strategy, verify that the right headline, source, update, image and content reached the page the reader and crawler receive.

I connect template acceptance to the agreed editorial and technical implementation. Select relevant templates/routes, verify information and discovery continuity and assign an owner for exceptions and retesting.

Facts and source, published content, version acceptance and separate discovery observation.
  1. Facts and source
  2. Published content
  3. Version acceptance
  4. Discovery observation

What the team retains

  • Fact, source, author and update acceptance appropriate to the content.
  • Useful HTML content, images and links verified on the selected templates.
  • A publication/change record separate from dated crawl/index observations and missing data.

Illustrative example: the headline changes but the correction note and source remain outdated. Repair information continuity and inspect the public version before treating a distribution fluctuation as the entire problem.

Accept publication against the defined result. Google News, Discover and AI inclusion remain platform decisions. Review those external observations separately without promising indexing time or exposure.

Next step

Discuss the technical search constraint

Bring the website URL, the affected pages and any Search Console or migration evidence you already have. We will define the next useful check, implementation ownership and how to verify it.

Who leads and implements the work

Portrait of Yaniv Goldenberg.10+ yrs operating
Yaniv GoldenbergFractional CMO · Head of Growth

I’m Yaniv Goldenberg. I lead strategy and personally implement the agreed work, with clear responsibility for approvals, acceptance and ongoing operation.

Work with Yaniv

Fractional Head of Growth for B2B SaaS, B2C, and e-commerce. Revenue that compounds, not spikes. Any channel, any motion, any stage.

By Yaniv Goldenberg, Fractional CMO & Head of Growth