| 开发者 | emrahsnkli |
|---|---|
| 更新时间 | 2026年9月11日 05:24 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
red-leather-handbag.jpg beats IMG_4827.JPG.<picture> element, so browsers that support it get the smaller file and caching plugins keep working.IMG_4827.jpg to something descriptive. Every generated size and every post that uses the image is updated, and the old URL sends a 301 redirect to the new one.IMG_4827.jpg. It is your own account, so you see the usage and the bill; nothing is proxied through us, and there are no credits to buy. A hard per-run limit (100 images by default) keeps a mis-click from running up a charge.
See the External services section below for exactly what is sent, and when.
Is there a Pro version?
Yes: PixelScore Pro - AI Image SEO and Alt Text Generator is a separate plugin that adds Anthropic Claude, Google Gemini and OpenRouter as alternative providers, plus AVIF delivery, WooCommerce product context, scheduled background runs and a CSV audit report. It is a different plugin with its own code — nothing in this one is disabled, limited or time-restricted.
/wp-content/plugins/ or install it from the Plugins screen.Only if you enable the optional AI alt text feature, and then only for the individual images you ask it to describe. It goes to the AI provider your site is configured to use — through the WordPress AI client on WordPress 7.0 and later, or directly to OpenAI with a key you saved yourself. With no provider configured the plugin makes no HTTP requests at all. Compression, resizing, WebP, scoring and renaming never leave your server under any configuration. The full disclosure is in the External services section above.
With "Keep a backup" enabled (the default) the untouched original of every file is copied into wp-content/uploads/pixelscore-backup/ before anything is changed. The Restore original button puts it back and re-scores the image.
It is the riskiest thing the plugin does, so it is never automatic. When you rename an image, PixelScore renames every generated size, updates the attachment record, rewrites the URL in every post that uses it, and stores a 301 redirect from the old path. The rewrite happens through the normal post update API, so a revision is created and you can roll a post back.
The dashboard tells you when that is the case. Scoring, compression, resizing, alt text and renaming all still work; only the WebP conversion is skipped. Ask your host to enable WebP support in GD or Imagick.
Whatever your own AI account charges for one small vision request per image. The image is downscaled to 768 pixels before sending, which is the cheapest input size that still describes reliably, and the default model is one of the smaller ones. A 3,000 image library is 3,000 requests, so set the per-run limit to something you are comfortable with before you start.
Only if the image deserves it. Decorative images that are not used on any page will legitimately lose the context points. The score is a diagnostic, not a target to game.
Scoring, compression, WebP and alt text work everywhere, because they operate on the media library. The URL rewrite after a rename only covers post_content, so if a builder stores image URLs in its own tables or post meta, check those pages after renaming.