Using yandex-pinger with Friendly URLs and SEO Strict URLs

How to avoid conflicts when a pinging tool sends ID-based URLs while SEO Strict URLs redirects everything to aliases.

Some external tools still prefer internal or ID-based links, while Evolution CMS projects often force friendly aliases with SEO Strict URLs. That combination can work, but only if the redirect behavior is expected and search engines are not being fed unstable variants.

The Core Issue

If a pinger submits resource URLs by ID, SEO Strict URLs will redirect them to the canonical alias-based version. This is usually fine, but it becomes noisy when the external tool expects one direct response and your site always answers through a redirect.

What to Verify

that the final destination URL is canonical and indexable
that redirects are permanent and consistent
that sitemap and ping tools use the same preferred URL style whenever possible

In short: avoid mixing canonical and non-canonical URL formats unless you have a good reason and have tested the full ping-to-index flow.

Newer post

Fixing “Too Many Forward Attempts” in Evolution CMS

What usually causes the “Too many forward attempts” error and how to trace redirect loops, forward chains, and broken fallback logic.

Older post

Planning Automatic Cloud Backups for Evolution CMS with Cron

A practical backup strategy for shared-host Evolution CMS projects: make a local dump, run it on cron, and push the archive to cloud storage safely.