Build · WordPress systems
My WordPress SEO & Performance Stack
I use Rank Math for on-page SEO at The Madrona Group, WP Rocket for WordPress performance on JasonFox.me, and Cloudflare across my websites. Here is the job each one does—and what none of them can do for weak content.
SEO software does not make a website rank. A caching plugin does not make weak content useful. These tools help me implement the technical work around pages worth finding.
From idea to evidence
- 01
SemrushResearch the question
- 02
Rank Math / SEO FrameworkImplement the on-page SEO layer
- 03
WordPressPublish useful content
- 04
WP RocketImprove delivery and performance
- 05
WP EngineHost the WordPress site
- 06
CloudflareManage DNS and the edge layer
- 07
Google Search ConsoleSee what actually happened
An honest note about this stack
Different sites. The same underlying jobs.
I use Rank Math for The Madrona Group. On JasonFox.me I am currently trying The SEO Framework instead. I am not claiming that Rank Math is installed here, or that one plugin has settled every SEO decision across every site I work on.
WP Rocket is active on JasonFox.me, where I can see the settings and test the results in an actual publishing workflow. Cloudflare is a consistent part of my websites, while the specific settings vary by site. The principle behind this page is more durable than any one plugin: research the topic, make the page useful, communicate its purpose to search engines, deliver it efficiently, and measure what happens.
The on-page layer
What I use Rank Math for.
On The Madrona Group, Rank Math gives me a place to manage how a WordPress page presents itself in search. I still have to make the editorial decisions.
Titles and descriptions
Write a search result that accurately describes the page and gives the right person a reason to click. This is not a place to cram in variations of a keyword.
Indexing and canonicals
Check whether a page belongs in search and which URL should represent it. Accidentally indexing thin or duplicate pages can make a site harder to understand.
Sitemaps and structure
Make the right content discoverable and keep the site architecture coherent. A sitemap helps discovery; it does not substitute for internal links.
Schema, where appropriate
Use structured data when it accurately describes the page. I do not add markup just to chase a rich-result promise.
Page-level checks
Notice missing metadata, weak headings, or other implementation details before publishing. The tool is a checklist, not the final editor.
The actual answer
Local knowledge, useful examples, clear writing, and a sensible next step are still human work. No SEO score can supply them.
I do not write for the Rank Math score. A score may flag something worth checking. It cannot tell me whether a buyer, seller, or agent found the answer they came for. I would rather publish a genuinely helpful page with an imperfect score than a hollow page with every light green.
The edge layer
Why Cloudflare is on every website I run.
Cloudflare is not an optional footnote to my WordPress stack. I use it across my websites as the layer between visitors and the origin.
Cloudflare is where I manage how a domain points to the right website and related services. That foundation matters before a visitor ever reaches a page.
Its network gives me site-level controls for traffic and delivery. The exact protections and performance features I turn on depend on the site; I do not assume one configuration fits every domain.
WP Engine hosts JasonFox.me. WP Rocket helps optimize the WordPress output. Cloudflare sits at the edge. I check how those layers interact rather than stacking overlapping cache settings and hoping for a better score.
Explore Cloudflare → (direct, non-affiliate link)
Two distinct jobs
Why I use an SEO plugin and a performance plugin.
The SEO layer
Does this page communicate what I intend? Is the title accurate? Should it be indexed? Does its canonical URL make sense? Is its structured data truthful?
Rank Math handles that work on The Madrona Group. The SEO Framework is the tool I am testing for that role on JasonFox.me.
The delivery layer
Is WordPress serving the page efficiently? Are images and embeds handled sensibly? Are CSS and JavaScript settings improving the experience without breaking functionality?
WP Rocket helps with this layer on JasonFox.me. It does not make the SEO or editorial choices.
Neither replaces Semrush research, Google Search Console, strong internal linking, local expertise, or the work of answering a real question.
The restraint
I do not install every optimization plugin I can find.
More tools are not automatically a better stack. Each one adds settings, overlap, and another place where something can break.
Two SEO plugins trying to control the same metadata or sitemap is confusion, not redundancy. I use one SEO layer per site.
A perfect lab number is not the business goal. I look for a real improvement in the visitor experience and check that forms, menus, and videos still work.
Too many heavy assets, poor hosting, or a site with no useful content cannot be fixed by stacking another plugin on top.
Performance options can alter how a page renders. I check the live page, not just the settings screen.
Who this is for
Use the tools that fit the site you actually run.
Rank Math makes sense if…
You run a WordPress site and actively manage titles, indexing, sitemaps, and page-level SEO. It is especially useful when those decisions are part of a repeatable publishing workflow.
WP Rocket makes sense if…
You run WordPress, performance needs attention, and you can test which caching and optimization features help your actual pages without disrupting them.
You may need neither if…
Your site is on a different platform, your host already handles the relevant performance work, or you are not publishing and maintaining a WordPress site. Start with the real bottleneck.
The connected system
Tools work best when the pages connect.
The plugin layer sits inside a larger real estate marketing system. These pages show the strategy, research, content, and technology around it.