--- title: "SEO for Custom-Built Websites in Jordan — What Developers Miss and How to Fix It" description: "Most custom-built websites in Amman launch with zero SEO — no robots.txt, no schema, JavaScript rendering failures. What developers miss and how to fix it." publishDate: "2026-06-07" lastModified: "2026-06-07" author: "Mohammad Khalil" authorRole: "Founder, SEO Amman Agency" category: "Platform SEO" readTime: 13 lang: "en" canonicalUrl: "https://seoamman.com/blog/custom-website-seo-jordan/" authorLinkedin: "https://www.linkedin.com/in/mohammad-khalil-algurus/" --- A real estate firm in West Amman had invested in a professional website. Custom-built. Beautifully designed. Detailed property listings for luxury apartments in Abdoun and villas in Um Uthaina. Neighbourhood guides. Contact forms. Everything a buyer would need — if they could find the site. They could not. Because the developer who built the website never created a robots.txt file. Google had no guidance on how to crawl the site. Over 10,000 pages sat in a non-indexed state. A website that represented a significant investment of money, time, and professional effort was completely invisible to Google. That firm was [Isam Khatib & Partners](/case-studies/ikhatib-partners-amman/). The missing robots.txt was a single file — a few lines of code — that no developer thought to create and no one audited for. The cost: years of invisible presence on Google while competitors captured every luxury property search in West Amman. At SEO Amman Agency, we have audited hundreds of custom-built websites across Amman, Jordan over thirteen years. The pattern is consistent and predictable: businesses hire a developer or a web agency to build a professional website. The site looks excellent. The functionality works. And Google cannot properly see, crawl, or rank any of it — because developers build for users, not for search engines. The SEO fundamentals that Google requires are not part of the typical web development scope unless the client specifically asks for them. This article is for every business owner in Amman who paid for a custom website and wonders why it does not appear on Google. The problems are specific, identifiable, and fixable. We have fixed them across dozens of client websites. Here is exactly what to look for. ## The Fundamental Disconnect: Developers Build for Users, Not for Google This is not a criticism of developers in Amman. It is a structural observation about how web development is taught, sold, and delivered. A developer's job is to build a website that works. Pages load. Buttons function. Forms submit. The design matches the mockup. The site displays correctly on mobile. These are the deliverables the client pays for and the standards the developer is measured against. SEO is not part of that scope. No client in Amman briefing a developer for a custom website says: "Make sure you create a robots.txt file, submit an XML sitemap to Google Search Console, implement LocalBusiness schema, write unique meta descriptions for every page, and ensure all JavaScript-rendered content is accessible to Googlebot." They say: "Build me a professional website for my business." The result is predictable: a website that works perfectly for humans who know the URL — and is partially or completely invisible to the search engine that would bring them every other customer. ## The Seven Developer Oversights That Make Custom Websites Invisible **Oversight 1: No robots.txt file.** The Isam Khatib case is the most extreme example in our portfolio — 10,000+ non-indexed pages because this file did not exist. But missing or misconfigured robots.txt is far more common than most business owners realize. A robots.txt file tells Google's crawler which parts of your website to access and which to skip. Without it, Google makes its own decisions — which, for complex sites with dynamic URLs, filter parameters, and admin areas, often means crawling the wrong pages and missing the right ones. The file itself is a few lines of text. Creating it takes five minutes. The Isam Khatib recovery — from 10,000+ non-indexed pages to 13 remaining — began with deploying this single file. Every [technical SEO](/services/technical-seo/) audit we run checks for robots.txt first. It is literally the foundation of Google's ability to process your website. **Oversight 2: No XML sitemap — or an auto-generated one that nobody checked.** An XML sitemap tells Google which pages on your site exist and which ones are most important. Without a sitemap, Google discovers pages only through crawling links — which means pages buried deep in the site structure may never be found. Many custom-built WordPress sites have an auto-generated sitemap from a plugin — but no one has ever verified what it contains. We regularly find sitemaps that include admin pages, draft posts, duplicate URLs, and attachment pages while excluding the actual service or product pages the business needs to rank. A sitemap is only useful if it accurately reflects the pages you want Google to index. The fix: manually review your sitemap. Remove any URL that is not a page you want to rank. Add any important page that is missing. Submit the clean sitemap to Google Search Console. This is a ten-minute task that most developers never perform. **Oversight 3: JavaScript content invisible to Googlebot.** This is the oversight we find most frequently on WordPress/Elementor websites — which represent a large share of custom-built sites in Amman. Elementor and similar page builders use JavaScript to render visual elements: counter animations, animated statistics sections, tabbed content panels, accordion sections, and slider carousels. These elements look impressive to a visitor with a browser. But Googlebot processes JavaScript differently — and in many cases, the content inside these elements is not rendered for the crawler. The most common and most damaging example: a "Results" or "Statistics" section using counter animations that display numbers like "200+ Clients" or "15 Years Experience." To a human visitor, the counter animates from zero to the target number. To Googlebot, the counter often renders as zero — because the JavaScript animation has not executed. Google sees a page with "0 Clients" and "0 Years Experience" — which is worse than having no statistics section at all. We find this exact pattern on a significant share of Amman business websites built with Elementor. The fix: test your website using Google's URL Inspection tool in Search Console. Click "Test Live URL" and then "View Tested Page" to see the rendered HTML as Google sees it. If any content shows as empty, zero, or missing, the JavaScript rendering is failing for that element. Replace JavaScript-rendered content with server-side HTML for critical SEO elements. **Oversight 4: Identical meta titles and descriptions across every page.** The default behaviour of many custom-built sites: every page has the same meta title — usually the company name — and either no meta description or the same generic description repeated across every page. When [Ritz Carlton Amman](/case-studies/ritz-carlton-amman/) came to us, every page on the site had generic or near-identical meta titles and descriptions. Room category pages, dining venue pages, the spa, events and weddings sections — all had meta tags that communicated nothing distinctive to Google about what each specific page offered. This is the [on-page SEO](/services/on-page-seo/) gap with the most direct ranking impact. Meta titles are the single strongest on-page ranking signal. A page with a meta title that matches the user's search query earns both better rankings and higher click-through rates than a page with a generic company name as the title. After rewriting meta titles and descriptions for every key page on the Ritz Carlton website — targeting both local Jordanian queries and international luxury travel queries — clicks grew from 652 in Phase 1 to 1,540 in Phase 2, a 2.4× increase. The content on the pages did not change. The meta tags that told Google and searchers what each page was about changed — and that was enough to more than double the click volume. **Oversight 5: No structured data of any kind.** Schema markup is the machine-readable layer that tells Google what type of business you are, what services you offer, where you are located, and what each page contains. Without it, Google has to infer everything from the visible text — which is slower, less accurate, and less complete than structured data provides. Most custom-built websites in Amman have zero schema markup. No LocalBusiness schema identifying the business. No Service schema describing what the business does. No FAQPage schema on FAQ sections. No BreadcrumbList schema for navigation. No Person schema for team members. [Isam Khatib & Partners](/case-studies/ikhatib-partners-amman/) had no structured data when we started. We implemented Organization, LocalBusiness, and BreadcrumbList schema across the site — giving Google machine-readable confirmation of the business entity, its location in West Amman, and the site's navigation structure. This is particularly important for real estate and other local service businesses, where entity authority directly affects local pack visibility. **Oversight 6: No heading hierarchy.** HTML heading tags — H1, H2, H3 — tell Google the structure and hierarchy of a page's content. The H1 is the page's primary topic. H2s are main sections. H3s are subsections. Google uses this hierarchy to understand what the page is about and which parts are most important. Custom-built websites frequently have broken heading hierarchies. Pages with no H1 tag. Pages with multiple H1 tags from conflicting page builder elements. Pages where the visual design uses large text that looks like a heading but is styled with div or span tags instead of proper heading tags — meaning Google sees no heading at all. Pages where H2 and H3 tags are used in random order based on visual size preference rather than content hierarchy. [O3 Ozoon](/case-studies/o3-ozoon-jordan/) demonstrated what happens when heading structure and on-page SEO are fixed on a business website built without SEO consideration: zero to 1,340 monthly clicks and 37,600 impressions in six months. The [on-page SEO](/services/on-page-seo/) work included fixing heading hierarchies across all category and service pages so that Google could properly understand the content structure. **Oversight 7: No Arabic content — on a website built for a Jordanian business.** This is not a developer oversight in the technical sense — it is a business decision that most Amman businesses make poorly. They hire a developer to build a website in English, launch it, and never add Arabic content. In a market where the majority of the population searches in Arabic, this means the website is invisible for every Arabic-language query related to the business. The [Isam Khatib & Partners](/case-studies/ikhatib-partners-amman/) engagement included Arabic keyword optimization for terms like 'شقق فاخرة عبدون' and 'فلل للبيع في عمان' — buyer-intent queries in Arabic that represent the highest-value prospects in the West Amman property market. Before the Arabic optimization, these searches returned zero Isam Khatib results. After: monthly organic clicks reached 1,360. The developer delivered a functional English-language website. The SEO work delivered Arabic visibility to an Arabic-speaking market. Both were necessary. Only one was included in the original development scope. ## WordPress/Elementor — The Most Common Custom Build in Amman A significant share of custom-built business websites in Amman are built on WordPress with Elementor as the page builder. This specific combination creates a predictable set of SEO issues we find repeatedly across client audits. **JavaScript counter animations rendering as zero for Googlebot.** Elementor's counter widget uses JavaScript to animate from zero to the target number. If Google's renderer does not execute the animation, the page displays "0" for every statistic. We find this on a substantial proportion of Amman business websites. **Multiple H1 tags from Elementor sections.** Elementor allows users to set any text element as an H1 heading for visual purposes. A page builder user who wants large, bold text naturally selects H1 — not realizing that multiple H1 tags on a page confuse Google about the page's primary topic. We regularly audit Elementor pages with three, four, or five H1 tags. **Elementor adding excessive inline CSS and JavaScript.** Elementor generates substantial inline CSS and JavaScript for each page's visual layout. This adds to page weight and loading time — a performance issue that compounds across a site with dozens of pages. Combined with unoptimized images and shared hosting, Elementor sites frequently fail Core Web Vitals thresholds on mobile. **Elementor's template system creating duplicate content patterns.** Elementor templates — headers, footers, and reusable sections — can create near-duplicate content across multiple pages if the same template content represents a significant portion of each page. Google may view pages with 60% identical template content and 40% unique content as near-duplicates. These issues are not reasons to avoid WordPress/Elementor — they are reasons to audit and configure it properly for SEO. The platform is capable. The default configuration is not. ## The Cost of Retrofitting SEO vs Building It In Every custom website that launches without SEO will eventually need SEO — if the business wants organic traffic. The question is whether the SEO fundamentals are built into the site during development or retrofitted afterward. Building SEO in from day one — as we did with [Perfu4me](/case-studies/perfu4me-jordan/) and [Tello Socks](/case-studies/tello-socks-jordan/) — means every architectural decision serves both users and Google simultaneously. URL structure, heading hierarchy, meta tags, schema, robots.txt, sitemap, image optimization — all configured at build time. The result: the site is indexable and ranking from the moment it launches. Retrofitting SEO afterward — as we did with Isam Khatib, Ritz Carlton, and O3 Ozoon — means diagnosing and fixing problems that were baked into the site's foundation. The robots.txt that was never created. The meta titles that were never written. The JavaScript content that Google cannot see. The schema that was never implemented. Each fix requires understanding what the developer built, identifying what is missing or broken, and implementing the correction without disrupting the existing functionality. Retrofitting works — every case study in this article proves it. But it costs more time and more budget than building SEO in from the start. Isam Khatib's engagement started with emergency technical remediation — three months of foundation work before any content optimization could take effect. If the robots.txt and schema had been included in the original development scope, those three months would have been spent on content and authority building instead. If you are about to commission a custom website for your business in Amman: include SEO requirements in the development brief. Specify: robots.txt, XML sitemap, unique meta titles per page, single H1 per page, schema markup, image alt text, and mobile performance targets. These are not SEO luxuries — they are the minimum requirements for a website that Google can process. Any developer can implement them during the build. Almost none will implement them unless asked. As we covered in our [Shopify SEO problems](/blog/shopify-seo-problems-jordan/) and [WooCommerce SEO problems](/blog/woocommerce-seo-problems-jordan/) articles, every platform has its own set of SEO issues. Shopify's are managed but limiting. WooCommerce's require active maintenance. Custom-built sites have the most freedom and the most risk — because there is no platform guardrail preventing fundamental oversights. ## Three Custom Website Recoveries — The Results **[Isam Khatib & Partners](/case-studies/ikhatib-partners-amman/) — Real Estate, West Amman** Starting point: 10,000+ non-indexed pages. No robots.txt. No schema. No Arabic content. After systematic [technical SEO](/services/technical-seo/) remediation: non-indexed dropped from 10,000+ to 13. Indexed pages reached 82. Monthly impressions: 22,600. Monthly clicks: 1,360. Arabic keywords 'شقق فاخرة عبدون' and 'فلل للبيع في عمان' now generating buyer traffic. **[Ritz Carlton Amman](/case-studies/ritz-carlton-amman/) — Luxury Hospitality** Starting point: generic meta tags across all pages, slow mobile performance, thin content on room and dining pages. After two-phase on-page and technical SEO: Phase 1 produced 652 clicks. Phase 2 — after mobile Core Web Vitals fixes — produced 1,540 clicks. 2.4× increase. Total: 2,270 monthly clicks, 77,300 impressions across 4 countries. **[O3 Ozoon](/case-studies/o3-ozoon-jordan/) — Men's Fashion, Amman** Starting point: zero indexed pages, incomplete GBP, no on-page optimization. After 6 months of [on-page SEO](/services/on-page-seo/) and local SEO: 1,340 monthly clicks, 37,600 impressions, 3.6% CTR, 7.3 average position. GBP rebuilt with 50+ photos and 30+ directory citations. Now ranking on page one for men's fashion searches in Amman. Three different industries. Three different websites. Three different developer oversights. All fixable. All fixed. All generating organic traffic that did not exist before the SEO work began. ## Closing If your custom-built website looks professional but is not generating organic traffic from Google, the problems described in this article are almost certainly present. We run a [free website SEO audit](/contact/) that checks your robots.txt, your sitemap configuration, your JavaScript rendering, your meta tag uniqueness, your heading hierarchy, your schema implementation, and your Arabic content coverage — and shows you exactly what your developer missed and how to fix it.