Technical SEO is the work of keeping a site findable, readable and singular at the right URL. Good copy still fails if the page is not crawled, the canonical points elsewhere, or the real content arrives late on the mobile template. Yuz Medya writes that floor in Istanbul as a priority list a developer can ship. We do not hand over a two-hundred-item PDF nobody reads. Templates that make money come first.
This is not a ranking promise. It is an engineering note that repairs crawl waste, index bloat, redirects, speed and markup. Markup is not a place to invent a star the page does not show. Schema has to match the price, the author or the event a visitor can see. If it does not match, it is not written.
Who it is for
It fits migrated sites, corporate structures that have piled on pages for years, storefronts built in JavaScript, bilingual URLs, and shops whose filters have opened without a rule. The symptom is usually the same. Excluded URLs grow in Search Console, old campaign links return 404, one piece of content has three addresses, and the publishing team says the page is live but absent from search. A deep technical program is not always the first job on a small brochure site. We look first at whether the page exists at all.
Store filters and variant URLs are a frequent shape of this work; the catalog intent itself runs in the ecommerce SEO brief. Service copy and mentions sit on the on-page and off-page SEO line. If the site will be rebuilt on Laravel or WordPress, the fix belongs in the WordPress / PHP software or corporate website calendar. We do not stack patches on a theme that is about to be replaced.
What we need before starting
A list written without access is a guess. If the developer, the host and Search Console are not at the same table, an item is marked done and never reaches production.
- The Search Console property, and hosting or server access where it is possible
- The templates that matter: home, service, category, product, article
- The known break: migration date, domain change, or a language added later
- Whether staging, if it exists, is closed to the index
- Who is allowed to ship a fix
- Which language is the primary URL when there are two
How Yuz Medya runs it
We crawl the templates money passes through first. A warning on the homepage does not share priority with ten thousand filter URLs. Each item carries three lines: what is broken, which template, and what should change once the fix is live. “Improve speed” is not an item on its own. We name the image, the third-party tool or the template part that holds the first screen.
If you implement, the list is cut into developer work with an acceptance check. If we implement, the same check is proven on staging and then released. We do not experiment on production. The monthly note is closed items and items postponed on purpose. The reason for a postponement is written, so “nobody looked” is not confused with “not this round”.
Scope
Scope is the technical layer that stops search from reading the page correctly. Rewriting the brand sentence or running a map profile does not replace this package.
- Crawl: robots, the sitemap, junk parameters and trap pages.
- Index: stray noindex, soft 404s, duplicate URLs and canonicals.
- Redirects: chains after a move, old campaign URLs, http and https.
- Speed: measured first screen on the templates that matter, image weight and heavy scripts.
- Language: hreflang only when both languages are actually live.
- Schema: organization, service, product or article markup that does not contradict the visible page.
Server logs help when they exist. When they do not, we proceed with Search Console and a bounded crawl. We do not put data in the report that we do not have. A Core Web Vitals score is not inflated into a league table. We write why the slow template is slow.
Method
A fix is not a page-by-page patch. If the fault is in a template, the template is fixed. Writing a canonical by hand on every product URL breaks again with the next product. The rule is set once, in the panel or the template. Filter and sort parameters are split into intents that may be indexed and combinations that may not. Without that split the sitemap swells and the real category thins out.
On a migration we look for a one-to-one home for the old URL. Pages with no successor are not dumped on the homepage. A 410 or an honest interim page is discussed instead. In language tags, Turkish and English have to point at each other. A one-sided tag is two sites arguing. In schema we do not invent reviews, prices or stock. A star that is not on the page is not in the markup.
Stages
Reading
Console coverage, a sample crawl and the template list go into one table. Symptom and cause are separated. “Not indexed” is not itself the cause.
Priority
Items fall into three groups: what cuts revenue, what dirties the template, and what can wait. The first slice stays small enough to ship. A forty-item sprint becomes a meeting where two items leave the room.
Ship and check
Redirects, canonicals and the sitemap are checked on staging. Sample URLs are read again after release. “The code was pushed” and “search sees the right URL” are not the same event.
Watching
In the following weeks, excluded URLs, 404s and template speed are read from the same list. A new plugin or a campaign landing page can break the floor again. We note that too.
What you gain
Developer and marketing look at one list. Old ad and email links do not stay broken. When duplicate URLs merge, the report calms down; three versions of one page no longer each “drop”. Speed work is felt on the template that matters. This is not a promise to rise on every query. With the floor straight, copy from on-page and off-page SEO is not written into a void.
Common mistakes
Leaving staging open to the index, forgetting a sitewide noindex, and canonicalizing everything to the homepage come first. Blocking CSS or scripts in robots, so the template looks empty to search, is the same family. Printing every filter combination into the sitemap bloats a shop. Chasing a perfect speed score while the H1 is empty reverses the priority.
There is a schema version of the same mistake: marking up reviews and ratings the page does not show. It is treated as a shortcut to a rich result. Markup that disagrees with the page creates risk, not trust. Yuz Medya does not recommend that path. Changing the domain on migration day without a redirect table asks the new site to rediscover an old history.
Related work, and a quote
Copy and internal links are the on-page and off-page SEO job. Branch pages and the profile talk to local SEO; the technical list also watches that those pages are not copies. On a store, the facet rule is written with the catalog plan. If the site will be rebuilt, the fix list becomes the acceptance check of the new template.
Send the address, the last migration or language change, and who can ship a fix, through the contact form. After discovery we name the first slice, what you will implement, what we will implement, and what stays outside this round. We do not promise a score. We name what is broken, and we check the fix after it is live.
What we deliver
- Technical SEO audit
- Speed / Core Web Vitals
- Schema markup
- Index and canonicals
- Mobile fitness
- Search Console tracking
Frequently asked about this service
No. The audit closes pages that cannot be found or that are slow, in priority order. Position also depends on competition and content. We do not turn that into a score promise.
No. The audit is the prioritized list. The fix is that item proven on staging and released. A team that only wants a report and a team that will ship are different scopes. We do not assume both in one price.
We do not promise that. We trim images, the template and third-party tools that are not earning their place. Hosting and the page’s own weight still matter. Improvement is shown as a before and after.
No. We write what slows the templates that matter and we reduce image and script weight. Third-party tools and hosting still move the score. We watch it as a measured template, not as a promise.
Crawl, index and speed are read on both. On WordPress we also look at plugins and archive pages. On Laravel we look at queries, redirects and whether the panel path is open to the index.
On most items, yes. Canonicals, redirects, the sitemap and template speed can be fixed in the current build. If the theme contradicts itself on every page, patches pile up. A rebuild is then the more honest path, and we say so in discovery.
The account stays yours. Yuz Medya reads coverage, speed and URL reports with the access you grant. If you change partners later, ownership remains with you.
It can, but there is risk when the real copy appears only after the client runs. We check that on a sample URL. If needed we write, with the developer, that critical content should also exist from the server. We do not condemn every framework in advance.
Yes. Search Console, the sitemap, status codes and sample templates show most of the priority. Logs make wasted crawl easier to read. The work does not wait on them.
Schema describes what the page is, and sometimes it is eligible for a rich appearance. It is not a ranking promise. We do not mark up reviews or prices that contradict the page. The type is chosen from information that is actually there.
No. We do not open a page for a district you do not serve. Auto-generated district copy is a doorway page. Technical work is not used to multiply those URLs.
Yes, for URLs that still have a successor. Old campaigns, email and search history point at the new address. We do not dump every unmatched URL on the homepage. Without a table, launch day starts with broken links.