DEV Community: Александр

Search Console warnings decoded: five worth acting on (and three to ignore)

Александр — Tue, 06 Oct 2026 10:52:45 +0000

Google Search Console means well, but it reports everything at the same volume. A missing hreflang tag and a hacked site get similar-looking red text. Here is a field guide: what deserves action today, and what you can safely stop worrying about.

Act on these

"Submitted URL returned 404" on important pages. If products or key landing pages return 404s, Google removes them from the index while customers still hold the bookmarks. Restore the pages or 301-redirect them to the closest live equivalent.
"Duplicate without canonical". Google found copies of a page and cannot tell which one to rank, so it picks — sometimes the wrong one. One canonical link per page solves it; e-commerce filters and pagination are the usual suspects.
Clickable elements too close together. On phones, taps land on the wrong link. Since most shop traffic is mobile, this is direct revenue damage, not a technicality.
"No hreflang return tags". If you run multiple languages, Google does not believe your language versions reference each other correctly — so it may show the French page to German buyers. Fix with correct hreflang pairs; the tags must be static HTML, identical for every visitor, or caches will serve half the pair.
Security actions (hacked content, malware). Drop everything else. This is the one warning that can remove you from search entirely.

Safe to ignore (or almost)

"Crawled - currently not indexed" for thin utility pages. Google saw them and chose not to rank them — for tag archives and parameter pages that is the algorithm working correctly.
Sitemap "couldn't fetch" flapping right after submission. Resubmit once, wait a week; it usually resolves itself.
"Page with redirect" occurrences. Informational: Google followed your redirects fine. Act only if a chain runs longer than two hops.

The weekly habit

Five minutes a week: open Coverage, sort by error, and ask one question — would a customer notice this? Customers notice 404s on products and broken mobile taps; nobody notices tag archives not being indexed. Treat Search Console as a to-do list where three items matter and the rest is ambience. And when a warning keeps appearing after you fixed it, check that the fix actually reaches Google's crawler — caches love serving old HTML.

Yodsira builds small, focused tools for jobs like this — browse the catalog.

This post is about a tool built by Yodsira — see the plugin page.

Originally published at Yodsira

Why PDF converters mangle Cyrillic (and how to pick one that doesn't)

Александр — Sat, 03 Oct 2026 15:05:56 +0000

If you work with Russian, Ukrainian, Bulgarian or any Cyrillic-language documents, you know the special failure: the layout survives perfectly, and the text inside reads as squares, mojibake, or question marks. The document is useless — you cannot search it, spell-check it, or copy a single correct name out of it.

Why it happens

A PDF does not have to store text at all — it can store drawings of letters. When it does store text, it maps glyph shapes to character codes through an internal encoding table. Good converters reconstruct that table and produce real Unicode text. Bad ones assume a single Western encoding, and every Cyrillic letter becomes whatever that byte means in Latin — the classic mojibake. The layout engine does not matter here: if the text mapping fails, prettier paragraphs are still garbage.

Second cause: fonts without proper Unicode tables embedded in the PDF — older scanners and 2000s-era Word exports. Third: OCR pipelines that recognize only Latin scripts, where Cyrillic falls back to the closest Latin shape. That last case is the most dangerous, because nothing looks broken: real words turn into plausible-looking wrong ones.

The one-minute test

Before trusting any converter with real work, feed it a test document and check three things in the DOCX output:

Copy test. Copy a sentence and paste it into a search box. If the word you know is there does not find the original document, the text layer is broken — no matter how good the output looks.
Mixed-alphabet test. A line like "invoice № 45" with both alphabets together. Weak converters drop or corrupt one of them.
Table test. A price table with Cyrillic headers. Cells must stay cells, headers must stay readable.

Run it once, and you know whether the tool respects your documents before it costs you a deadline. Our own PDF to Word converter is built around exactly these cases — Cyrillic and Latin intact, tables preserved, everything processed locally on your machine — but the test works with any converter, including free ones. Whatever you use: the paste-into-search check is the ten seconds that separate a working document from a nice-looking pile of garbage.

If you would rather not wire this up by hand: this is exactly what PDF to Word does.

This post is about a tool built by Yodsira — see the plugin page.

Originally published at Yodsira

Never Miss a Sale: Send WooCommerce Order Notifications to Telegram

Александр — Wed, 30 Sep 2026 10:06:45 +0000

You paid for ads, the customer paid for the order — and then you found out about the sale three hours later from a support ticket. If that sounds familiar, your email notifications are quietly costing you money. Order emails get spam-filtered, delayed, or swallowed by hosting mail queues, and every lost notification means slower response, a missed upsell window, or a customer who buys elsewhere next time. The fix is simpler than it sounds: add Telegram as a second, independent channel for order alerts.

Why email alone fails (and why it's not your fault)

Email was never designed to be instant or guaranteed. Between your store's server and your inbox sit spam filters, blacklists, and half-broken mail settings that can silently drop messages.

Spam filters. Automated order notifications look exactly like the bulk mail filters love to quarantine.
Hosting mail limits. Many shared hosts rate-limit outgoing email, so a burst of orders can sit in a queue for minutes or hours.
Silent failure. When an email doesn't arrive, you get no error. You just don't know about the order.

The point isn't to abandon email — it's to stop depending on a single point of failure.

Why Telegram works as a backup channel

Telegram messages land on your phone in seconds, they don't pass through the same spam pipeline as email, and the setup itself is free. You can send alerts to yourself, to a private team chat, or both. And because notifications arrive where you already read messages, you'll actually see them — no more “another tab I never check.”

Setup checklist: from zero to instant alerts

The whole thing takes under half an hour, even if you've never touched a bot before.

Step 1. Create your Telegram bot

Open Telegram and search for @BotFather — the official bot for creating bots.
Send /newbot and follow the prompts. Pick something clear like MyStore Orders.
BotFather gives you a token — a long string that is the key to your bot. Copy it and keep it private.

Step 2. Get your chat ID

Send any message to your new bot so the conversation exists.
Get your numeric chat ID — the easiest way is a lookup bot like @userinfobot, or your plugin may detect it automatically during setup.

Step 3. Connect it to WooCommerce

In your WordPress admin, go to Plugins → Add New and search for Telegram notifications WooCommerce.
Pick a plugin with a solid rating and recent updates, then install and activate it.
Paste in the bot token and your chat ID.
Choose which events trigger alerts: at minimum New order and Failed order. Add Refunded and On hold if they matter to your workflow.
Hit the send test message button. If it appears in Telegram, you're connected.

Step 4. Place a real test order

Don't trust the test button alone. Push a cheap product through a real checkout (or a test payment gateway) and watch what arrives in Telegram — and how fast.

Make it actually reliable

A backup channel only helps if it works when you need it. Run through this before you call it done:

Retest after updates. Plugin conflicts can silently break notifications. One test order after a WooCommerce or plugin update is cheap insurance.
Use a group chat for teams. Add whoever fulfills orders — everyone sees the sale at once, no forwarding, no “I didn't get the email.”
Keep email enabled. Telegram is your backup, not your replacement. Customers still get receipts by email, and you keep a paper trail.
Protect your token. Anyone with it can send messages through your bot. Don't paste it into chats, docs, or screenshots.
Check Do Not Disturb. Set an exception for Telegram, or at least for the bot chat, so late-night orders still reach you.

Honest conclusion: Telegram notifications won't grow your sales by themselves — they just remove the delay and blindness between a customer paying and you acting. You still have to process orders, reply to people, and watch your store. But for twenty minutes of setup you get a channel that doesn't depend on spam filters or your host's mail server — and that alone saves you from the worst kind of problem: a paying customer you didn't know about.

Originally published at Yodsira

This post is about a tool built by Yodsira — see the plugin page.