Dev.to WebDev 🛠 Dev 👁 0 📖 2 min read

How I built an SEO-ready WordPress and Elementor agency site (and took PageSpeed from 87 to 98)

I'm Jagdeep Singh Rana, a web developer from Roorkee, India. Ragnar Studio's (https://ragnarstudio.com/) is my own web design, Shopify and SEO studio in Dehradun, and I built its website myself on WordPress and Elementor

I'm Jagdeep Singh Rana, a web developer from Roorkee, India. Ragnar Studio's (https://ragnarstudio.com/) is my own web design, Shopify and SEO studio in Dehradun, and I built its website myself on WordPress and Elementor. Here is what actually moved the needle.

1. Structure first: pages that match how people search

Instead of one generic "Services" page, the site has dedicated pages for each service, city and industry, for example web development in Dehradun (https://ragnarstudio.com/web-development-company-dehradun/), Shopify store development (https://ragnarstudio.com/services/websites/shopify-store-development/) and SEO in Dehradun (https://ragnarstudio.com/seo-company-dehradun/). Each page has one clear H1, one intent and its own FAQ.

2. Schema and llms.txt

Service pages ship JSON-LD (Organization, Service, FAQPage, BreadcrumbList). I also added an llms.txt file so AI assistants get a short, accurate summary of the business instead of guessing from the HTML.

3. Performance: from 87 to 98 on mobile

Elementor sites are heavy by default. A small performance layer made the biggest difference: preloading the LCP image, hoisting critical styles, delaying non-essential JavaScript until interaction, handling popups without blocking rendering, and tuning font loading. The home page went from 87 to 98 and a typical blog post from 83 to 99 in PageSpeed Insights.

4. Measure leads, not just visits

I fire a GA4 generate_lead event from a small WPCode snippet when someone clicks WhatsApp, calls or submits the form, so Search Console traffic can be tied to real enquiries.

5. A caching gotcha worth knowing

My sitemap index briefly returned a 404 to Google because LiteSpeed had cached a 404 response. Purging cached 404s fixed it. If Search Console reports "Couldn't fetch" for a sitemap that loads fine for you, check your page cache first.

Takeaways

  • Build one page per search intent.
  • Add schema and llms.txt early.
  • Treat performance as a feature, not a final polish.
  • Track leads from day one.

You can see the result at https://ragnarstudio.com/ and my other work at https://jagdeepsinghrana.online/. Questions about WordPress, Shopify or SEO? Leave a comment and I will reply.

📰 Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.