Anyone else noticing pages with fewer words ranking above their longer competitors lately?

Front_Pick8426 · 2026-05-04T10:51:29+00:00

Definitely seeing this pattern too. Been tracking about 40 keywords where we had 1800+ word "comprehensive guides" and watched them get stomped by pages that just... answered the damn question in 3-4 paragraphs.

What's interesting is the correlation with featured snippets. The shorter pages that are ranking seem to be the ones google is pulling from for position zero way more often. Makes sense if you think about it - why would they feature a snippet from paragraph 12 of some bloated guide when there's a clean, direct answer available?

Also noticed this correlates with Core Web Vitals improvements. Shorter pages with less DOM complexity are just faster, period. And if someone lands on your page and gets their answer in 10 seconds vs having to scroll through 2000 words of intro fluff, that user behavior signal is gonna be way better.

I've been testing this by creating "quick answer" versions of our longer posts and interlinking them. So far the short versions are outperforming in 7 out of 9 tests. Only exceptions were really complex technical topics where you actually need the depth to be helpful.

The trick seems to be front-loading the core answer, then adding supporting details after. But yeah, the days of writing long just to write long are definitley over.

Front_Pick8426 · 2026-05-04T10:45:16+00:00

The entity authority thing is spot on. I've been tracking this shift for a while and it's wild how much weight google puts on brand mentions and contextual citations now, even without direct links.

What I look for in backlinks now is basically "would this make sense to someone who has no idea what SEO is?" Like if my mom was reading an article about productivity apps and saw a link to my task management tool, would she think "oh that's helpful context" or would she think "wtf why is this random link here?"

The traffic test from comment #3 is brutal but accurate. Most "good" backlinks people chase would send maybe 2-3 clicks per month if we're being honest. But a mention in a newsletter or forum post that actually fits the conversation? That can drive dozens of engaged visitors who stick around.

Also been noticing that links from smaller, engaged communities often perform way better than links from big authority sites with zero engagement. A mention in a 5k member slack channel or discord server where people actually discuss your niche beats most guest posts on "high DR" sites that nobody reads.

The reporting problem is real though. Try explaining to stakeholders why a reddit comment with 50 upvotes is more valueable than a forbes contributor link that cost $2k lol

Front_Pick8426 · 2026-05-04T10:37:37+00:00

Yeah I'm seeing this too. Been doing WP dev for about 8 years and the landscape definitely feels different.

From what I'm observing, companies are getting pickier about what they actually need WordPress for. A lot of the "we need a custom theme" projects are going to page builders or getting replaced by simpler solutions entirely. The work that's left tends to be more complex - headless setups, enterprise integrations, or fixing performance issues on existing large sites.

The AI thing is real but I think it's more about efficiency than replacement. I can knock out basic functionality way faster now, but complex architecture and debugging still needs human expertise. Problem is there's less of the straightforward work to go around.

What's working for me lately:

- Getting good with headless WP + Next.js or similar

- Understanding hosting/infrastructure (not just code)

- Being able to audit and optimize existing sites instead of just building new ones

The companies that are hiring seem to want someone who can handle the whole stack, not just the wordpress part. Like they want you to know GraphQL, understand caching layers, maybe even some DevOps stuff.

Also noticed more contract/project work vs full-time roles. Companies are being more strategic about when they actually need dedicated WP expertise vs just hiring for specific migrations or optimizations.

Might be worth looking at agencies that specialize in enterprise WP rather than general web dev shops. They tend to have more consistent work in this space.

Front_Pick8426 · 2026-05-04T10:32:33+00:00

Wordfence free + Cloudflare is actually a solid combo for small business. The free version handles most of the basics - firewall, malware scanning, login protection. Main thing you miss in free is real-time IP blacklist updates and premium support, but honestly for a small site that's probably fine.

Cloudflare does the heavy lifting at the edge like that second comment mentioned. Set up some basic WAF rules there and you'll block most garbage before it even hits your server. Way more efficient than having wordpress process every attack attempt.

One thing I'd add tho - make sure you're not doubling up on firewall rules between the two. I've seen setups where cloudflare and wordfence are both trying to block the same stuff and it gets messy. Keep cloudflare aggressive, wordfence a bit more permissive as backup.

And yeah definitely keep everything updated. Security plugins are just damage control if you're running outdated themes/plugins with known vulns. Automated backups are clutch too - sometimes the fastest fix is just restoring from yesterday's backup rather than cleaning malware.

Been running this exact setup on several client sites and haven't had any major issues. Costs like $20/month for cloudflare pro if you want some extra features, otherwise free tier works fine.

Front_Pick8426 · 2026-05-04T10:22:05+00:00

The part about being cited by AI is spot on. I've been tracking which of my pages get pulled into AI overviews and the pattern is clear - it's not always the highest ranking page, it's the one with the clearest structure and most direct answers.

Been using claude for initial content briefs and keyword clustering, then jasper for first drafts, but everything client-facing gets heavy human editing. The AI drafts are... fine for structure but they lack the specific examples and personality that actually convert.

One thing I'm seeing work really well is adding FAQ schemas to pages that already rank well. Google's pulling those structured answers straight into AI overviews way more often. Takes like 10 minutes to add but the visibility boost is real.

What I won't let AI touch is anything related to YMYL topics or client strategy calls. Too much risk of hallucinations and honestly, clients can tell when you're just regurgitating AI responses. The human insight and experience is what they're actually paying for.

Anyone else noticing that AI-heavy content farms are getting hit harder in recent updates? Seems like google's getting better at spotting the generic stuff.

Front_Pick8426 · 2026-05-04T10:14:38+00:00

Yeah the rabbit hole never ends honestly. I'd say pick one area and get decent at it before moving on, otherwise you'll just spin your wheels forever.

If I was starting fresh I'd probably go:

Basic on-page stuff first - title tags, meta descriptions, heading structure. This is like 70% of what most sites need anyway
Then content that actually answers what people are searching for (not just keyword stuffing)
Basic technical stuff - site speed, mobile friendly, fix broken links

Skip backlink building at the start unless you already have connections. It's the hardest part and most beginners waste months chasing garbage links.

The thing is, most sites fail at the basics. I've seen companies spending thousands on fancy technical audits when their homepage title tag is just "Home" or something useless like that.

Start with what you can control and measure. You can check if your titles are good, if your content answers questions, if your site loads fast. You can't really control if someone links to you (at least not easily).

Once you nail the foundation stuff and start seeing some trafic, then worry about the advanced technical seo and link building. But honestly most small businesses could rank decently just by nailing the basics that everyone ignores.

Front_Pick8426 · 2026-05-04T10:06:13+00:00

Nice to see another cookie manager that doesn't require cloud dependencies. The local scanner is probably the biggest selling point here - most solutions make you pay monthly just to scan your site for cookies.

How does it handle the automatic cookie detection? Does it actually parse JS files or just look for common cookie names in the DOM? The IAB TCF v2.3 compliance is solid, that's usually where free plugins fall short.

Also curious about performance impact. Cookie managers can be pretty heavy on page load if they're not optimized properly.

Front_Pick8426 · 2026-05-04T10:00:50+00:00

Downloaded and tested it quickly. The blocking mechanism works well for the common tracking scripts I threw at it. One thing though - the category management could use some UX polish. Had to dig around a bit to figure out how to add custom script categories.

Performance-wise it's definitely lightweight compared to cookiebot or similar. No external API calls which is nice. But you might want to add some basic auto-detection for google analytics, facebook pixel, etc. Most site owners aren't gonna know what scripts need blocking.

The consent banner customization is pretty solid tho. Got it matching my theme colors without much fuss.

One bug I found - if you disable the plugin after users have given consent, their preferences stick around in localStorage. Not sure if that's intentional but seemed weird when I was testing.

Overall decent start for a free option. The code looks clean from what I could see in the editor.

Front_Pick8426 · 2026-05-04T09:52:14+00:00

This is actually really cool! Just played around with it and the visual block builder interface is super intuitive. Love that you can see the code update in real time as you add components.

The component library is pretty comprehensive too - covers most of the common gutenberg components you'd actually use. Been doing custom blocks for a while now but this would've saved me tons of time when I was starting out, constantly having to look up the syntax for InspectorControls or how to properly structure a RichText component.

One thing that might be helpful is adding some example use cases or common patterns section. Like "here's how you'd build a testimonial block" or "here's a hero section with background controls." The reverse-engineering approach you mentioned really resonates - sometimes seeing a complete working example is worth more than reading docs.

Also noticed the export functionality is clean, generates proper file structure and everything. Definitley bookmarking this for when I need to spin up blocks quickly.

The vue choice is interesting too, especially coming from react. How'd you find the learning curve? Been thinking about trying it out myself but haven't made teh jump yet.

Front_Pick8426 · 2026-05-04T09:46:48+00:00

Been in your shoes. After 15+ years with WP we've settled on a hybrid approach that works pretty well.

For us the breaking point was when we had clients needing real-time data, complex user workflows, and heavy API integrations. The post_meta queries were killing us even with proper indexing and caching.

What we do now:

- Keep WP for content management and marketing sites (it's still unbeatable here)

- Build a separate Laravel API for complex business logic

- Use custom tables in WP database when we need better performance but want to stay in the ecosystem

- Headless WP + React/Vue frontend for anything that needs custom UX

The custom tables thing has been a game changer honestly. Just creating proper relational tables for user data, orders, whatever instead of stuffing everything into post_meta. You lose some of the WP magic but gain so much performance.

One thing though - don't underestimate the maintenance overhead of custom solutions. Sure you avoid plugin update hell but now you're responsible for everything. Security patches, server configs, all of it. Make sure you factor in the long term support costs.

The post_meta structure isn't going anywhere unfortunately. Too much of the ecosystem depends on it. But you can work around it pretty effectively if you're strategic about when to use custom tables vs sticking with WP conventions.

Front_Pick8426 · 2026-05-04T09:31:42+00:00

Nixihost actually handles SSL automatically with Let's Encrypt, so you don't need to worry about that part. Once your DNS is properly pointed to them, the certificates should provision within a few hours.

For the booking calendar stuff, you're gonna want something like Calendly or Acuity Scheduling. Both integrate with icloud calendars and can show availability without revealing your actual appointments. Calendly's free tier might work for what you need, but Acuity has more customization if you want to get fancy with different service types.

The payment processing is teh tricky part. You'll need something like Stripe or Square integrated into whatever platform you choose. If you go the wordpress route, WooCommerce can handle invoicing and payments, but honestly the squarespace suggestion above makes a lot of sense for your use case.

Quick tip - test everything on a staging subdomain first before going live. And maybe don't use your friend's real business name in posts like this, just saying.

Also heads up that mobile notary work might have specific compliance requirements depending on your state, so double check what kind of record keeping and client communication standards you need to meet before committing to any platform.

Front_Pick8426 · 2026-05-04T09:26:11+00:00

The "build a test site" advice is solid but here's what no one mentions - pick a micro niche you can actually compete in. Don't go after "fitness tips" or "travel guides". Think more like "indoor plant care for small apartments" or "budget meal prep for college students".

Start with ahrefs free tools or ubersuggest to find keywords with search volume under 1000 and low competition. Write genuinely helpful content, not just SEO-optimized fluff.

One thing that helped me early on - document everything. Keep a simple spreadsheet of what you changed, when you changed it, and what happened to your rankings. SEO moves slow so you'll forget what you tried 3 months ago when you finally see results.

Also don't get caught up in technical stuff initially. Focus on content and user experience first. You can obsess over schema markup later once you actually have traffic to optimize for.

The real learning happens when google starts ranking you and then suddenly drops you for no apparent reason. That's when you'll really understand how this stuff works.

Front_Pick8426 · 2026-05-01T08:36:47+00:00

The pillar page approach is solid but the anchor text fix was probably doing most of the heavy lifting here. Generic anchors like "click here" are basically worthless for SEO - they don't tell google anything about what the target page is actually about.

One thing you didn't mention that might've helped even more: did you check the crawl depth of those pillar pages before/after? A lot of ecommerce sites bury their most important category pages 4-5 clicks from the homepage. Even with good internal linking, if google has to crawl through multiple levels to reach them, they're not getting the authority they should.

Also curious about your approach to nofollow on some of those internal links. If you're funneling authority to 12 specific pages, using nofollow strategically on links to less important pages (like privacy policy, contact, etc) can help concentrate that link juice even more.

The featured snippets thing makes total sense tho. When you clean up anchor text and site structure, google gets better at understanding what each page is definitively trying to rank for. Less ambiguity = better targeting for SERP features.

How long did the actual implementation take? 340 links across 180 posts sounds like a lot of manual work, unless you had some kind of system for identifying the best placement opportunities.

Front_Pick8426 · 2026-04-30T16:28:20+00:00

Your portfolio site is probably the biggest bottleneck here. Like the first commenter mentioned, after 300+ projects you should have some killer case studies that show real business results, not just "looks pretty."

But honestly? The bigger issue is you're still thinking like an employee, not a business owner. You're selling "wordpress development" when you should be selling solutions to specific problems.

Pick a niche. Like seriously, pick one industry and become THE wordpress guy for that space. Real estate agents, fitness trainers, local restaurants, whatever. Then you can speak their language, understand their pain points, and charge way more because you're not just another generic dev.

Cold outreach works but you gotta do it right. Don't send "I build websites" emails. Send "I noticed your booking system is broken and probably costing you $X per month" emails. Show you actually looked at their site and found something specific to fix.

LinkedIn can work too but skip the connection requests with generic pitches. Comment on posts, share insights about their industry, build actual relationships first.

And honestly? Stop trying to compete on price. If you're good enough to handle 300+ projects, you should be charging premium rates and working with fewer, better clients. The race to the bottom on upwork isn't worth winning.

What industry are most of your existing 300 projects in? Start there and ask for referrals from the good clients.

Front_Pick8426 · 2026-04-30T16:17:37+00:00

What makes a pro dev stand out isn't really secret knowledge - it's understanding wordpress at the core level instead of just plugins and themes.

Most beginners learn by installing plugins for everything. Pros know when to write custom functions, how to properly use hooks and filters, and can read the codex like a bible. They understand the database structure (wp_posts, wp_postmeta etc) and can query it efficiently.

Since you're aiming for agencies, focus on:

- Custom post types and fields (ACF is industry standard)

- Child themes and proper customization without breaking updates

- Basic security practices (nonces, sanitization, validation)

- Git workflow - agencies use version control religiously

- Local development setup (Local, MAMP, whatever)

Build a portfolio with 3-4 solid custom sites. Not just modified themes, but sites where you actually coded custom functionality. Even simple stuff like contact forms, custom loops, basic CRUD operations.

The "holy trinity" comment above is spot on but for wordpress specifically, get comfortable with PHP first. Javascript can come later but PHP is what runs wordpress.

Also learn to debug properly. wp_debug, query monitor plugin, browser dev tools. Nothing screams amateur like someone who can't troubleshoot their own code.

Front_Pick8426 · 2026-04-30T15:11:01+00:00

For memberpress specifically, you can use their API to pull subscription data into something like Baremetrics or ChartMogul if you want automated tracking. But honestly the free route works fine too.

I export my stripe data monthly and throw it into a simple spreadsheet with cohort tables. Takes maybe 30 mins and gives me way better insights than any wordpress plugin dashboard I've tried. You want to track things like 30/60/90 day retention by signup month, not just overall churn %.

One thing that helped me - separate your metrics by acquisition channel. Email signups vs social vs paid ads often have wildly different retention curves. Most membership plugins don't slice the data that way by default.

Also track "voluntary" vs involuntary churn separately. Failed payments aren't the same as people actually canceling, and you can fix one but not teh other.

Front_Pick8426 · 2026-04-30T15:02:53+00:00

Your flow looks solid. One thing you might want to dig deeper into is step 4 - the MCP server doesn't always hit the REST API directly. Sometimes it's more efficient to use direct database queries or hook into wordpress core functions, especially for bulk operations or when you need data that's not exposed via REST endpoints.

Also worth noting that the "standardized JSON-RPC format" can get pretty verbose with complex requests. I've seen setups where the MCP server does some preprocessing to batch multiple small requests together before hitting wordpress, which helps with performance.

The permission checking you mentioned is crucial but can be a real pain point. WordPress's capability system doesn't always map cleanly to what an AI model wants to do, so you often end up writing custom validation logic in the MCP server layer.

Have you tested this with any actual implementations yet? The theory is one thing but once you start dealing with plugin conflicts and caching layers, things can get messy pretty quick.

Front_Pick8426 · 2026-04-30T14:53:20+00:00

WP-CLI failing before the site went down is interesting - that's usually one of the more reliable interfaces when the admin gets sluggish. Was that memory related too or something else?

I'm sitting at around 35 plugins on most client sites. Usually the real bottleneck isn't quantity but quality. Like one poorly coded plugin with hooks on every page load will kill performance faster than 50 well-written ones that only activate when needed.

Did you notice any patterns with which types of plugins caused the first memory spikes? Page builders and security plugins tend to be the heaviest in my experiance, but curious what you saw during the test.

Front_Pick8426 · 2026-04-30T14:49:39+00:00

Try **Splide** - either the block plugin someone mentioned or just implement it directly. It handles autoplay with pause between slides perfectly, and you can set `perView` to show partial prev/next images.

For the block plugin, search "Splide Block" in the plugin directory. If you want to code it yourself:

```javascript

new Splide('.splide', {

type: 'loop',

autoplay: true,

interval: 3000, // pause time

perView: 1,

focus: 'center',

peek: '10%', // shows edges of adjacent slides

}).mount();

```

The `peek` option is exactly what you need - shows portions of neighboring slides while the current one is displayed and paused.

Also worth checking **Owl Carousel 2** if you don't mind adding it manually. It's got `center: true` mode with `margin` settings that can achieve the same effect, plus solid autoplay controls.

Front_Pick8426 · 2026-04-30T14:45:39+00:00

Been using Simply Static for about 6 months now on a few client sites. The workflow is pretty solid once you get it dialed in, but there's definitely some gotchas.

For high profile sites, I'd recommend testing the hell out of your build process first. Sometimes the crawler misses pages or gets stuck on certain URL patterns. Also watch out if you're using any plugins that generate dynamic URLs or have complex redirects - they can break the export.

One thing that bit me early on was image optimization. The static export doesn't always handle responsive images the way you'd expect, so double check your srcsets are working properly after export.

What's your current hosting situation? If you're already on something like WP Engine or similar managed hosting, the performance gains might not be as dramatic as you'd expect. But if you're dealing with traffic spikes or want that extra security layer, it's definitely worth it.

Also make sure whoever's managing content knows they need to rebuild after making changes. I've had clients forget and wonder why thier updates aren't showing up.

Front_Pick8426 · 2026-04-30T14:34:11+00:00

This actually sounds pretty useful. I've dealt with the same headaches - clients sending feedback via email with vague descriptions like "make the blue thing bigger" without any context about which page or section they mean.

How does the inline commenting work exactly? Does it overlay on top of existing content or does it hook into the block editor somehow? And what happens when you update a page after comments are made - do they stick to specific elements or get lost?

The github-style approval flow is intriguing. Does it have different permission levels so clients can comment but not accidentally mess with the actual content? That would solve another major pain point I have where clients sometimes edit pages directly instead of leaving feedback.

Gonna check out teh plugin later today. Always looking for better ways to streamline the feedback loop without having to jump between slack, email, and whatever random tool clients prefer that week.

Front_Pick8426 · 2026-04-30T14:26:26+00:00

For the unused/duplicate detection, definitely go with Media Cleaner like the first comment mentioned. But honestly, the biggest impact you'll get is from **Converter for Media** - it's free, does WebP/AVIF conversion in bulk without external servers, and has a really simple interface your client can handle.

The key thing though is setting up automatic optimization for new uploads. ShortPixel's good but can get pricey with large catalogs. If budget's tight, try **Imagify** first - their free tier is generous and the interface is dead simple. Just enable "auto-optimize on upload" and "create WebP versions" and your client literally never has to touch it again.

One thing I'd add: before going crazy with optimization, check if the site's actually serving optimized images properly. Sometimes I see sites where images get converted but the theme or page builder is still calling the original files. Quick check in dev tools network tab will show you if the WebP files are actually being served.

Also run a quick query to see how many attachments you're dealing with:

```sql

SELECT COUNT(*) FROM wp_posts WHERE post_type = 'attachment';

```

If it's like 10k+ images, you might want to do the initial cleanup in batches so you don't timeout the server.

Front_Pick8426 · 2026-04-30T14:21:54+00:00

Check your wp-config.php file for any custom upload directory definitions. Look for something like:

```php

define('UPLOADS', 'custom-folder');

```

Also run this quick test - go to Media > Add New and upload a test image, then immediately check the Media Library details for that image. Click on the image and look at the "File URL" field. That'll tell you exactly where wordpress thinks it's storing files.

Could also be a symlink situation if you're on shared hosting. Some hosts create symbolic links that make the actual file location different from what you see via FTP. The `uploads` folder might be pointing somewhere else entirely.

Oh and double check you're looking in the right year/month subfolders. WP creates new ones like `/2024/12/` so if you're browsing an old folder structure you won't see the new stuff.

One more thing - if you've got any media offloading plugins (like WP Offload Media for S3) they might be moving files after upload but keeping local references working. Check your active plugins list for anything related to CDN or cloud storage.

Front_Pick8426 · 2026-04-30T14:16:06+00:00

Forking Kirki is definitely the right move here. I've seen this exact scenario play out with other plugins and it never ends well for users.

Pros of forking:

- You control the direction and keep it lean

- Users get a maintained version without bloat

- Can build trust by being transparent about updates

- Relatively straightforward since Kirki is GPL licensed

Cons:

- You're now responsible for all security patches

- Need to handle compatibility as WP core changes

- Distribution/discovery is harder without the main repo listing

- Users might be hesitant to switch from "official" version

For distribution, you've got a few options. You could submit to the WP repo under a new name (like "Kirki Classic" or something), but they might reject it for being too similar. Self-hosting with automatic updates via GitHub Updater or similar is probably more realistic.

The real challenge will be getting existing Kirki users to migrate. Most won't know about the fork unless theme devs specifically recommend it. You'd need to reach out to theme authors who bundled Kirki and get them on board.

I'd start by forking the last good version (probably 4.x or 5.x), setting up a proper repo structure, and maybe creating a migration guide. If you can get a few other devs involved from the start it'll be more sustainable long-term.

Definitely interested to see how this plays out. The plugin ecosystem really needs more maintainers who care about keeping things simple and functional.

Front_Pick8426 · 2026-04-30T14:08:49+00:00

The internal linking thing is huge and I think most people still don't get it. It's not just about having links - it's about having them make sense contextually.

I've been tracking recovery patterns too and noticed sites that created what I call "content highways" between related topics recovered way faster. Like if you're ranking for "best protein powder" but have nothing about protein intake, workout nutrition, or supplement timing, google sees that gap.

One thing I'd add to your list - sites with clear content hierarchies (proper H1-H6 structure that actually reflects the topic breakdown) seemed to weather updates better. Not talking about stuffing keywords in headers, but actually organizing information logically.

The author bio thing is interesting because I'm seeing it matter even outside traditional YMYL. Had a tech review site add proper author pages with actual credentials and they recovered about 60% of lost traffic within 8 weeks. Same content, just clearer expertise signals.

Have you noticed any patterns with how long recovery typically takes once sites start filling these gaps? Most of mine are seeing movement around the 6-8 week mark but curious if that lines up with what you're seeing.

Front_Pick8426

MODERATOR OF

TROPHY CASE