DEV Community: Дарья

ChatGPT Is My #1 Traffic Source: What That Means for SEO in 2026

Дарья — Sat, 12 Sep 2026 04:50:22 +0000

Six months ago, Google was my primary traffic source. Today it is ChatGPT.

My Apple Watch wallpaper site gets about 70 sessions per week:

Source	Sessions/week
ChatGPT	20
Direct	19
DuckDuckGo	10
Bing	7
Facebook	6
Perplexity	2
Google	1

What Happened to Google

Duplicate hreflang tags across 195 translated pages caused a deindexation event in July 2026. Fixed within a week, but Google still shows 7 pages indexed out of 82.

ChatGPT crawled my site, liked the content, and started recommending it — no hreflang required.

How ChatGPT Finds Content

Direct answers. Quick Answer boxes at the top get cited most.
Structured content. Tables, lists, clear H2 headings.
Specificity. Narrow topics outperform broad overviews.
Freshness. New articles get ChatGPT traffic within days.

What I Changed

No special tricks. Just clear structure:

Quick Answer box at top
Table of Contents with anchors
FAQ sections with schema
Narrow topics over broad guides
Data tables and comparisons

AI assistants have different ranking criteria than Google. You need clear, structured answers — not backlinks.

More on content structure: watchwalls.pro/blog

Building a Dynamic XML Sitemap That Scales Beyond Plugin Limits

Дарья — Mon, 07 Sep 2026 04:47:06 +0000

When your WordPress site hits 50+ posts, your SEO plugin's sitemap starts dropping pages. I found out the hard way — my site had 75 posts, but only 49 showed up in post-sitemap.xml.

The Plugin Ceiling

Rank Math Free generates sitemaps automatically. But it has an undocumented limit on entries per sitemap file. Post #50 pushes post #1 out. No warning, no error — just silent removal.

I only noticed because Google Search Console showed "Discovered - currently not indexed" for pages that used to rank. They'd been quietly removed from the sitemap weeks earlier.

The PHP Solution

Instead of fighting the plugin, I built a supplementary sitemap that catches everything the plugin misses:

<?php
header('Content-Type: application/xml; charset=utf-8');
require_once(__DIR__ . '/wp-load.php');

$posts = get_posts([
    'post_type' => 'post',
    'post_status' => 'publish',
    'posts_per_page' => -1
]);

// Fetch existing plugin sitemap URLs
$xml = @file_get_contents(home_url('/post-sitemap.xml'));
preg_match_all('/<loc>([^<]+)<\/loc>/', $xml, $matches);
$existing = array_flip($matches[1] ?? []);

echo '<?xml version="1.0" encoding="UTF-8"?>';
echo '<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">';

foreach ($posts as $post) {
    $url = get_permalink($post);
    if (!isset($existing[$url])) {
        $mod = get_the_modified_date('Y-m-d', $post);
        echo "<url><loc>{$url}</loc>";
        echo "<lastmod>{$mod}</lastmod></url>";
    }
}
echo '</urlset>';

Key Design Decisions

Why not just increase the plugin limit? Rank Math Free doesn't expose that setting. The Pro version does, but I didn't want to pay for one config option.

Why check against the existing sitemap? To avoid duplicates. Google handles duplicate URLs gracefully, but clean sitemaps build more crawler trust. The array_flip trick makes the lookup O(1) instead of searching an array on every iteration.

Why posts_per_page => -1? Because we need every published post, not just the first 10. Yes, this loads all posts into memory. For 75 posts it's fine. For 10,000 you'd want pagination.

Deployment

Drop the PHP file in your WordPress root (alongside wp-config.php)
Add it to robots.txt: Sitemap: https://yoursite.com/ww-sitemap.php
Submit in Google Search Console alongside your main sitemap
It regenerates dynamically on every request — no cron needed

Results After 2 Weeks

Before: 49 URLs in sitemap, 26 posts invisible to Google
After: All 75 posts discoverable
Bing indexed the missing pages within 48 hours via IndexNow
Google... is still thinking about it (6 weeks and counting)

The full story of how this fit into a larger indexation recovery effort is on my site: watchwalls.pro/apple-watch-wallpaper-guide

Has anyone else hit plugin sitemap limits? Curious what solutions you found.

How I Used AI to Generate 500+ Apple Watch Wallpapers (And What I Learned About Tiny Screens)

Дарья — Wed, 02 Sep 2026 05:54:26 +0000

Most wallpaper generators are built for phones and desktops. Nobody thinks about the 374×446 pixel screen on your wrist. So I built one.

The Problem With Resizing

I tried generating Apple Watch wallpapers with Midjourney, DALL-E, and Stable Diffusion. Every single image came out at 1024×1024 or 16:9. Cropping a square image to a ~5:6 portrait rectangle means losing 40% of the composition.

After 50+ attempts of "generate, download, crop, upload to watch, realize it looks terrible, repeat" — I decided to build the pipeline differently.

What Actually Works for Tiny Screens

Three rules I learned after generating 500+ watch wallpapers:

1. Simple compositions beat complex ones.
A detailed cityscape that looks amazing on an iPhone becomes an unreadable smudge on a 41mm watch. One focal point, dark background, high contrast — that's the formula.

2. Dark backgrounds save battery (literally).
Apple Watch uses OLED. Pure black pixels (#000000) are physically turned off — no light, no power drain. A wallpaper with a dark base and one bright element gives you the best of both worlds: looks great AND saves 10-15% battery per day.

3. Portrait orientation from the start.
Don't generate square or landscape and crop later. Set your canvas to 374×446 (or 416×496 for the larger model) from the beginning. The AI fills the space differently when you give it a tall, narrow canvas versus a square.

The Resolution Table Nobody Publishes

Every Apple Watch model has slightly different pixel dimensions. I spent way too long figuring these out:

Model	Size	Resolution
Series 10 (42mm)	1.74"	374 × 446
Series 10 (46mm)	1.96"	416 × 496
Ultra 2	1.93"	410 × 502
Series 9 (41mm)	1.7"	352 × 430
Series 9 (45mm)	1.9"	396 × 484
SE (40mm)	1.57"	324 × 394
SE (44mm)	1.78"	368 × 448

Best AI Prompts I Found

These consistently produce good results for watch-sized screens:

"dark nebula with purple and blue swirls, centered bright star, portrait orientation, dark background"
"single koi fish swimming in dark water, top-down view, minimal"
"geometric gold lines on matte black background, abstract, portrait"
"underwater coral reef, dark ocean background, bioluminescent glow"
"northern lights over dark mountain silhouette, portrait orientation"

The key is always including "dark background" and "portrait orientation" in your prompt.

The Tool

I packaged all of this into WatchWalls AI — it generates wallpapers at the exact resolution for your watch model. No cropping, no guessing. Describe what you want, pick your model, get a wallpaper.

Full guide on generating AI wallpapers for Apple Watch: watchwalls.pro/apple-watch-ai-wallpaper

What's your experience with AI-generated wallpapers for small screens? Curious if anyone has found prompts that work even better.

I Built a PHP Sitemap That Fixed My Google Indexation Problem

Дарья — Sat, 22 Aug 2026 15:40:37 +0000

My WordPress site has 65 posts, but Rank Math's sitemap was only showing 49. The remaining 16 posts were invisible to Google. Here's how I fixed it with a 30-line PHP file.

The Problem

Rank Math Free limits post-sitemap.xml to a fixed number of entries. When I published post #50, it silently pushed post #1 out of the sitemap. Google eventually deindexed the missing pages.

The Fix: `ww-sitemap.php`

I created a PHP file in my WordPress root that generates a sitemap dynamically from the database, excluding any URLs already in Rank Math's sitemap (to avoid duplicates):

<?php
header('Content-Type: application/xml; charset=utf-8');
require_once(__DIR__ . '/wp-load.php');

$posts = get_posts(['post_type' => 'post', 'post_status' => 'publish', 'posts_per_page' => -1]);

// Get existing sitemap URLs to avoid duplicates
$xml = @file_get_contents(home_url('/post-sitemap.xml'));
preg_match_all('/<loc>([^<]+)<\/loc>/', $xml, $m);
$existing = array_flip($m[1] ?? []);

echo '<?xml version="1.0" encoding="UTF-8"?>';
echo '<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">';

foreach ($posts as $post) {
    $url = get_permalink($post);
    if (!isset($existing[$url])) {
        $mod = get_the_modified_date('Y-m-d', $post);
        echo "<url><loc>{$url}</loc><lastmod>{$mod}</lastmod></url>";
    }
}
echo '</urlset>';

Then I submitted ww-sitemap.php in Google Search Console alongside the existing sitemap_index.xml.

The Result

Before: 49 URLs in sitemap, 16 posts invisible to Google
After: All 65 posts discoverable
Bing picked up the missing pages within 48 hours via IndexNow

Lessons Learned

Always verify your sitemap contains all your pages — don't assume the plugin handles it
Dynamic PHP sitemaps are a valid fallback when plugin settings aren't accessible
Submit supplementary sitemaps in GSC — you can have multiple

Site: watchwalls.pro — an Apple Watch wallpaper resource where I discovered this problem.