| 开发者 | phillipb |
|---|---|
| 更新时间 | 2026年8月6日 17:44 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
LocalBusiness with AggregateRating) so search engines can show star ratings for your site.[ratingstar] shortcode or the RatingStar Seal block — or switch on the site-wide seal.
Customising the look: every embed accepts the appearance attributes produced by the embed generator in your RatingStar portal (for example pc-color, car-count, footer-bar-bg). Use them as shortcode attributes ([ratingstar variant="carousel" car-count="4"]), paste them into the block's "Embed attributes" field, or into the site-wide settings — seal.js validates the values.
Why it stays fast and clean:
seal.js) is loaded asynchronously and only on pages that actually contain a seal.AggregateRating is never duplicated.ratingstar-de-seal folder to /wp-content/plugins/, or install the ZIP via Plugins → Add New → Upload Plugin.ratingstar.de/t/). The slug is verified against your live profile. Optionally add your API key (rs_live_…) for the rename-proof key-based endpoints.TXT _ratingstar.<domain> DNS record — otherwise the seal data may be blocked with HTTP 403.[ratingstar variant="profile-card"] or the RatingStar Seal block — or enable the site-wide seal in the settings.It is the last part of your public profile URL: https://ratingstar.de/t/<slug>. Enter just the <slug> part on the settings page.
The round seal and the banner seal are static and work on every plan. Profile card, trust bar, hero snippet, featured quote, carousel, wall of love and footer bar are live widgets and need a 4-star plan or higher — on lower plans seal.js shows the banner seal instead.
Open the embed generator in your RatingStar portal, configure the widget and copy the resulting attributes into the shortcode, the block's "Embed attributes" field or the site-wide settings. The data- prefix may be included or left out; invalid values fall back silently.
Make sure a profile slug is saved under Settings → RatingStar and that the page contains the [ratingstar] shortcode, the RatingStar Seal block or an enabled site-wide seal. Check that your domain is whitelisted and DNS-verified in the RatingStar backend. If you use a caching or "remove unused JavaScript" plugin, make sure seal.js from ratingstar.de is not blocked.
Yes. The rating data for the JSON-LD is cached server-side for 6 hours via a WordPress transient, so page caches stay light. The seal itself renders client-side from live data; the static image is cached by CDN and browser.
The seal widget loads seal.js and rating data from ratingstar.de, so visitors' browsers connect to that domain when a seal is shown. Mention this in your privacy policy and, if you use a consent solution, treat ratingstar.de accordingly. The server-side Google review stars (JSON-LD) do not require any client-side connection; the static image mode only requests a single image.
The seal works with your public profile slug alone. The API key (format rs_live_… from your RatingStar backend) is recommended for the Google review stars: it drives the rename-proof key-based endpoints, which keep working when your profile slug changes and are open on all plans.
LocalBusiness JSON-LD, cached for 6 hours, duplicate-free.