Custom-built websites break SEO rules that platforms handle automatically.
Most agencies never notice. We do this deliberately.
Shopify generates canonical tags. WooCommerce creates sitemaps. WordPress handles basic schema. Custom-built websites do none of this automatically. Every SEO rule that a CMS or e-commerce platform handles for you needs to be implemented deliberately — in code, in server configuration, or in whatever CMS your developers built. When it is not, the site has structural SEO problems that no amount of content or link building will overcome. We have resolved these problems for custom-built websites across Jordan and the UAE — and in our experience, fixing the technical foundation produces the most dramatic ranking improvements of any SEO work we do.
Direct Answer
Custom-built website SEO requires a deeper technical audit than any off-the-shelf platform — we have fixed crawl architecture, server-side rendering issues, and Arabic URL encoding problems on custom sites across Jordan and the Gulf that no standard CMS plugin could address.
8 SEO Problems Custom Websites Have That Platforms Handle Automatically
Hreflang implementation
Bilingual Arabic/English custom sites almost always have broken hreflang — either missing entirely, pointing to the wrong language versions, or using incorrect region codes. Google relies on hreflang to understand which page to serve to which audience. When it is broken, Arabic pages can be invisible to Arabic searches even when the content is correct. We fixed this for Thiqa Education UAE and it unlocked months of suppressed Arabic indexation.
Canonical tag logic
Without canonical tags, any page that can be accessed via multiple URLs — paginated content, filtered views, URL parameters, printer-friendly versions — creates duplicate content signals. Custom sites generate these situations constantly. Without deliberately implemented canonical tags, Google sees the same content on dozens of URLs and does not know which to rank.
Sitemap generation
A static custom website either has no sitemap or one that was manually created at launch and never updated. A dynamic custom site needs sitemap generation logic built into the application. Without an accurate, up-to-date sitemap, Google's ability to discover and crawl all your pages depends entirely on internal linking — which is rarely sufficient for large sites.
Schema markup injection
Search engines use structured data (JSON-LD schema) to understand what a page is about — an article, a product, a service, an organisation. Custom sites have no schema unless a developer explicitly built it in. Missing schema does not prevent ranking, but it reduces your eligibility for rich results and makes it harder for Google to understand your content at scale.
Arabic URL encoding
Arabic-language URLs need to be either transliterated into English or properly percent-encoded. Custom sites built by non-specialist developers often produce Arabic URLs with encoding errors that render differently across browsers, create duplicate content problems, and are difficult for Google to crawl. We resolve this at both the technical and server configuration level.
Core Web Vitals on custom frameworks
Custom-built applications — especially those using React, Angular, or Vue without server-side rendering — often have significant LCP and INP issues because the browser must download, parse, and execute JavaScript before anything appears on screen. This creates poor Core Web Vitals scores that suppress mobile rankings. Platform sites are not immune, but custom apps are disproportionately affected.
Crawl budget management
Large custom sites — especially those with dynamic URL generation, user-generated content, or complex filtering systems — can produce millions of URLs from a relatively small content base. Google allocates a fixed crawl budget per site. When that budget is consumed by worthless dynamically-generated pages, valuable content pages go un-crawled for weeks or months at a time.
Structured data for non-standard content types
A custom education platform, a custom healthcare portal, or a custom B2B service site has content types that do not fit neatly into standard WordPress post categories. Custom schema needs to be designed and implemented for how the content is actually structured — courses, practitioners, services, accreditations. This is developer and SEO work that no plugin can handle.
How We Diagnosed and Fixed Thiqa Education's Custom Website
From near-zero organic visibility to 3,040 monthly clicks in six months.
Thiqa Education operates a custom-built bilingual website serving learners in the UAE. When they came to us, their site had been live for some time — but organic search was almost non-existent. The issue was not the content. The content was strong. The issue was structural, and it was invisible unless you knew exactly where to look.
Hreflang implementation errors. The custom site had hreflang tags, but they were pointing to incorrect language-region combinations — telling Google that the Arabic pages were English and vice versa. As a result, Google was not indexing the Arabic pages correctly. Months of Arabic content had been written and published with almost no organic Arabic impressions.
Complete hreflang audit and rebuild. We also restructured the URL architecture to cleanly separate Arabic and English content, and submitted a coverage request to Google Search Console to accelerate re-indexation of the Arabic pages.
While the technical foundation was being repaired, we built the content strategy: 300+ keyword bilingual keyword map, separate Arabic and English content tracks for every programme page, and a content cluster of 8 pillar pages and 20+ supporting articles targeting programme-specific search queries in both languages.
By month six: 3,040 monthly organic clicks and 109,000 monthly impressions at an average position of 7.1. Arabic pages — which had been generating almost no impressions — became a major traffic source. The hreflang fix alone unlocked a content asset that had been invisible for months.
Read the full case study"We started appearing more and more on Google, and AI tools began recommending Thiqa Education to students searching for courses. The SEO strategy Mohammad Khalil built for us has made a real difference in how we're discovered online."
Platform vs Custom: The Honest SEO Comparison
Neither is universally better. Each creates different SEO challenges.
| Aspect | Platforms (WP/Shopify) | Custom |
|---|---|---|
| Technical SEO defaults | Good — canonical, sitemap, schema handled | None — all must be implemented |
| Flexibility for complex content | Limited — constrained by platform | Unlimited — designed for your needs |
| Bilingual handling | Plugin-dependent, often incomplete | Can be perfect — if built correctly |
| Page speed baseline | Depends on theme/plugins | Depends on architecture decisions |
| Ongoing SEO maintenance | Manageable with right partner | Requires developer + SEO collaboration |
| Fix complexity | Usually fast | Can require development work |
Custom websites done well can outperform any platform on every SEO metric. The challenge is that 'done well' for SEO requires deliberate technical decisions at the build stage — decisions that are rarely made without SEO input.
Questions About Custom Website SEO
Our custom site was built by a development agency. How do we know if it has SEO problems?+
The most reliable way is a technical SEO audit — we crawl the site, review Google Search Console data, check hreflang implementation, review canonical tag logic, assess page speed, and identify indexation issues. In our experience, most custom-built sites have at least two or three of the eight issues listed above. The hreflang problem alone — which Thiqa Education had — can suppress an entire language version of a site for months.
Do we need our developers involved in custom website SEO?+
For technical fixes, yes — there are changes that require code-level implementation. We work alongside your development team to specify the required changes, provide the exact implementation instructions, and verify that the fixes are correctly deployed. For content strategy, keyword research, and on-page optimisation of existing pages, developer involvement is not required.
Our site is Arabic-only. Do we still need hreflang?+
If your site is single-language, hreflang is not relevant. But an Arabic-only site often has other structural issues: Arabic URL encoding problems, missing sitemap, no schema markup, and crawl budget issues from dynamically-generated URLs. The specific problems depend on how the site was built — which is why we always start with an audit.
Can you do SEO for a custom site built on a framework like Laravel or React?+
Yes. We have worked with custom sites built on various frameworks. The framework determines how technical fixes need to be implemented, but the SEO principles are the same. React and other single-page application frameworks create specific crawlability challenges that we address with server-side rendering recommendations and pre-rendering strategies.
Is custom website SEO more expensive than platform SEO?+
Not necessarily. If the technical foundation of the custom site is sound, the ongoing SEO work is similar in scope to a platform site. The difference is that the initial technical audit and fix phase for custom sites is often more involved — because there are more potential structural issues to discover and more that require developer collaboration to resolve.
Start with a Technical Audit
Custom website SEO starts with understanding exactly what the site is doing wrong — and right. We will audit your custom site's technical SEO foundation, identify the specific issues affecting your rankings, and give you a prioritised fix list. No obligation.
Request a Free Technical SEO Audit