AstroWay – Astrology, Birth Chart & Horoscope Widgets

Paste one shortcode into a page and the horoscope is on it: real text, in your theme's own fonts and colours, inside the HTML that search engines read. No frame, no JavaScript, no account, no API key, no credit card. Three steps to the first widget

1. Install and activate. There is nothing to configure and nothing to sign up for.
2. Paste this into any post or page: [astroway_daily_horoscope sign="leo"]
3. Open the page. The reading is there, styled like the rest of your content.

The moon phase takes no parameters at all, [astroway_moon_phase]. A birth chart takes a date, a time and a place: [astroway_natal date="1990-05-15" time="14:30" lat="50.45" lon="30.52" tz="Europe/Kyiv"] AstroWay → Shortcodes in your admin lists every shortcode with its parameters and a copy button, next to a city search that fills in coordinates and timezone for you. Every one of them is a Gutenberg block as well: type /astroway in the editor and the preview shows the finished card, not a placeholder. What needs a key

• Nothing at all: daily, weekly and monthly horoscopes, moon phase, Tarot card of the day, planet of the day, the natal chart with its reading, the Human Design bodygraph, the moon sign, the rising sign, synastry, the four sky cards (Mercury retrograde, all retrogrades, void of course Moon, planetary hours), the yearly horoscope, sign compatibility, the Chinese animal and the birth-data calculators. On first use the plugin asks api.astroway.info for a key of the site's own, proving it owns its address; there is nothing to sign up for. The site gets 300 readings an hour, and each answer is cached until the data changes.
• A free key, no card: 10,000 credits a month. It adds the 680 generated shortcodes. Most calls cost 10 credits.
• A paid plan, from $5 a month: more credits and a higher rate limit for busy sites. The daily transit alert email needs the Pro plan.

What renders into the page Eleven widgets are rendered by your own server directly into the page: daily, weekly and monthly horoscopes, moon phase, Tarot card of the day (Rider-Waite deck), planet of the day, the natal chart, the Human Design bodygraph, the moon sign, the rising sign and the synastry between two charts. Their text is part of your HTML, so search engines index it, screen readers announce it, and it inherits your theme's fonts and colours instead of sitting in a frame that ignores them. The natal chart's wheel, its aspect grid and its element matrix are drawn into the page as well, in the same colours as the text around them. Each answer is cached until the underlying data actually changes, so a page carrying all twelve signs spends twelve requests a day rather than twelve an hour. This runs on the anonymous per-site allowance of 300 requests an hour, with no key and no account. What the sky is doing right now Four cards answer the questions people search for rather than calculate: is Mercury retrograde, what else is retrograde, is the Moon void of course, and which planetary hour is it. [astroway_mercury_retrograde] prints yes or no, the dates of the retrograde it is in or heading for, and how many days are left. [astroway_retrogrades] does the same for all eight planets that station, as one table. [astroway_moon_voc] lists the void windows with their last aspect and next sign. [astroway_planetary_hours latitude="50.45" longitude="30.52"] prints the twenty-four hours of the day with the one you are in marked. Station and window times are printed on your site's clock, not in UTC, which matters more often than it sounds: Saturn turns direct at 23:31 UTC on 10 December, and that is the 11th anywhere east of Greenwich. They run on the site's own key, which the plugin asks for by itself. Calculators for your visitors Leave the date out and a card asks for it. [astroway_natal], [astroway_moon_sign] and [astroway_rising_sign] with no birth date show a short form, and [astroway_synastry] with no dates asks for two people: date, time, and the city, found by name with its coordinates and time zone. The answer is drawn on the same page by your server, so the form works without JavaScript. Without a birth time the natal chart leaves out houses and the Ascendant rather than guessing noon, the moon sign names both signs on a day the Moon changed sign, and the rising sign says plainly that it needs the time. The plugin keeps nothing a visitor types: the answer is not cached and the page is sent no-store and noindex. What a natal chart means Under the chart, each planet in its sign has its reading: edited texts from AstroWay's own astrologer, in the site's language, one row per planet. Planet in house and the aspects follow as they are written, and a row simply does not appear until its text exists. 680 more, for when you need them Eighteen widgets are hand-built and need no key. Behind them the plugin also carries a shortcode and a block for 680 more endpoints: Vedic charts and dashas, four kinds of numerology, three tarot decks, BaZi, Zi Wei Dou Shu, Human Design, geomancy, runes, Mayan calendars, astrocartography, horary, and the Hellenistic traditions. AstroWay → Shortcodes lists them by family with a copy button on each. They are generated from the API specification rather than written one by one, so when the API gains an endpoint the plugin gains a shortcode. These need an API key; a free key comes with 10,000 credits a month, and most calls cost 10 of them. The year, two signs, and the Chinese animal Three cards read the signs themselves. The yearly horoscope, [astroway_yearly_horoscope sign="leo"], prints the year ahead. [astroway_zodiac_compatibility sign1="leo" sign2="aquarius"] prints how two signs read together, as prose rather than as a percentage: the API returns no score, and a number with no calculation behind it is worse than no number. [astroway_chinese_zodiac date="1990-05-15"] prints the animal of a birth year with its element, polarity and pillar. Two charts, read against each other The synastry card, [astroway_synastry name_a="Olena" date_a="1990-05-15" time_a="14:30" name_b="Marc" date_b="1988-11-02" time_b="09:15"], prints the compatibility score in a ring with the word the API puts on it, the Sun, Moon and Ascendant of each person, and both charts on one bi-wheel: the first inside with its houses, the second on the outer ring, and the aspects between them as lines. Every aspect names whose planet is whose, because "Moon conjunct Mercury" says nothing until you know whose Moon, and says in a line what that kind of contact does between two people. The six closest are listed and the whole grid, points included, is one tab away. A birth time you do not have is declared unknown rather than guessed at noon, which would move the Moon by up to six degrees and invent an aspect that is not there. The names never leave your server. No key needed; one of these counts as five requests of the hourly allowance, because it is the grid between the two charts and each chart on its own, and it is cached for a month. Add transits="today" to a natal chart, or a date such as transits="2026-10-01", and it gains a Transits tab: the birth chart inside, the sky of that day on the outer ring, and the transits within three degrees listed tightest first. Tabs, without the JavaScript Put several AstroWay blocks inside an Astrology Section and set its layout to Tabs. Your server still renders every card, one after another, and a 3 KB script folds that stack into a proper tab strip with arrow-key navigation. Turn JavaScript off and the page is the stack it always was, with every word still in the HTML: nothing is fetched in the browser and nothing is hidden from a crawler. Tab labels drop the words they all share, so four horoscopes for one sign read "today", "the week", "the month" and "the year". An email when the sky does something Turn on daily transit alerts under AstroWay → Settings and your site emails you on the days a planet stations or the Moon goes void of course, with the current retrogrades and the moon phase for context. Nothing is sent on the quiet days, which is the point: a message every morning is a newsletter, and this is an alert. Pick the hour on your own clock and who it goes to. Part of the Pro plan. One sign for a whole section The Astrology Section block sets a zodiac sign once and every AstroWay block inside it follows: four horoscopes on a sign's landing page, and the sign is written in one place rather than four. A block that has its own sign keeps it. What still loads in a frame Widgets that have no page-side template yet, and any widget whose data cannot be fetched at that moment, fall back to an embedded frame loaded by the visitor's own browser (30 requests/hour per visitor IP). Eighteen widgets need no key of any kind, and that is where most sites stop. The generated shortcodes behind them need one: a free key gives 10,000 credits a month, most calls cost 10, and paid plans raise the limits further. The daily transit alert email is the only thing in the plugin that asks for a paid plan. Under the hood the widgets are powered by api.astroway.info, with 700+ endpoints covering Western, Vedic, Hellenistic, Chinese and Mayan astrology, Tarot (Rider-Waite, Marseille, Lenormand), Numerology (Pythagorean, Chaldean, Kabbalistic, Tamil), Human Design and AI horoscopes. Try it before you install The same calculations run as free web tools, with no install and no account: a birth chart and a synastry comparison. Useful for seeing what a widget will output before you put a shortcode on a page.

1. Upload the plugin via Plugins → Add New, or unzip into /wp-content/plugins/, then activate it through the Plugins menu.
2. Paste a shortcode into any post or page: [astroway_daily_horoscope sign="leo"], or type /astroway in the block editor.
3. Open the page. Nothing else is required: no account, no API key, no configuration.

Optional: AstroWay → API Key, to paste a key from api.astroway.info. Every widget works without one; a key is what you use when you call the API yourself.

2.2.0

• Synastry on a bi-wheel: both charts on one wheel, the first inside with its houses, the second on the outer ring, and the aspects between them as lines
• The synastry card shows the score in a ring, the Sun, Moon and Ascendant of each person, and each aspect with whose planet is whose and what it does between two people
• A synastry shortcode without dates asks the visitor for two people, on the same form as the other calculators
• A natal chart with transits="today" or a date gains a Transits tab: the sky of that day on the outer ring and the transits to the birth chart
• Connect your AstroWay account in one click from the Getting started page, instead of copying a key
• Fix: synastry with a place but no time zone read the birth time as UTC; it now takes the zone of the place, as the natal chart does
• Tabs stay on one row on a phone and fade at the edge that has more; the element matrix has its own heading; the retrograde mark no longer sits on a degree
• Every new string translated in all 20 bundled languages

2.1.0

• Calculators for visitors: a natal chart, moon sign or rising sign shortcode without a date asks for one, with a city search, and draws the answer on the same page without JavaScript
• An unknown birth time is handled honestly: no houses, Ascendant or Moon aspects, both moon signs on a day the Moon changed sign, and no rising sign
• The natal chart has its reading: each planet in its sign, in the site's language
• The site gets a key of its own from api.astroway.info by proving it owns its address; the retrograde, void of course, planetary hour, yearly horoscope, compatibility and Chinese animal cards now work without an API key
• The admin panel titles keep their line on a phone

2.0.0

• Natal chart, aspect grid and element matrix are drawn into the page instead of loaded in a frame
• Horoscope card: sign medallion, twelve signs as links, day/week/month tabs, date arrows
• Moon, moon sign, rising sign, planet of the day, retrogrades, void of course Moon and planetary hours rebuilt on the same components
• One table for every card: stacked rows on a phone, a scroll hint, and the row you are in marked for screen readers
• Three looks: Instrument, Night and Theme colours, chosen in Settings or per shortcode with look=
• Plugin notices have their own close button; closing snoozes them instead of silencing them, and a review can be marked as already left
• Both lat/lon and latitude/longitude work in every shortcode
• Links to api.astroway.info open in the admin's language, and in English when the site does not have it
• Sites in a language the API does not speak get English readings instead of Ukrainian
• Every new 2.0 string translated in all 20 bundled languages, and the element and sign names earlier machine translations got wrong fixed

1.5.6

• Fix: a visitor who ran out of the per-IP allowance of a framed widget saw a card telling them to get an API key. The frame now folds away for visitors, and only administrators see a note saying why.
• Fix: framed widgets (the natal wheel, numerology, kundli, panchang and transits) are light by default, no wider than your content column, and as tall as their content. theme="dark" still gives the dark version.
• Fix: the generated shortcodes answer in your site's language, or in the one set with lang. Before, they answered in Ukrainian on sites in other languages.
• Fix: a natal chart given coordinates but no tz was calculated in UTC. It now uses the timezone of the place; the moon sign, rising sign and bodygraph cards do the same.
• Fix: tables no longer run past the card on narrow screens, and a table that scrolls shows that it does.
• Fix: tab labels in an Astrology Section start with a capital letter.
• Change: the widget stylesheet loads only on pages that show a widget. A theme that prints a widget from a template can load it in the head with the astroway_load_styles filter.
• Change: the API key is stored encrypted and shown masked, and it can be set in wp-config.php with define( 'ASTROWAY_API_KEY', '...' );.
• Change: blocks have their own AstroWay category in the inserter, and the generated ones are marked "(API)".
• New: deleting the plugin removes its settings and cached data.

1.5.5

• Change: the message about a publishable key now points at api.astroway.info/dashboard/keys, the page that lists your keys, rather than the dashboard front page. Translated in all 20 bundled languages.

1.5.4

• Change: the refusal shown for a publishable key now also says where the right one is. Both keys, the publishable and the secret, are listed on your dashboard at api.astroway.info/dashboard/.
• Translations: that message is now carried in all 20 bundled languages. The four strings of the Domain binding panel are corrected in every one of them as well, where "Rebind key" had been translated as a key on a keyboard and "Rebinding" as binding a book.

1.5.3

• Fix: a publishable key, the kind that starts with pk_live_ or pk_test_, could not be saved, and the reason given was that a key must start with "aw_". On a key copied correctly that reads like a typo. Such a key is now recognised and refused with the real reason: it is meant to sit in page source and the API accepts it only from a browser on one of its allowed origins, while this plugin calls the API from your server. Secret keys are unaffected.

1.5.2

• Fix: the "Rebind key" button on the Domain binding panel never worked. It posted to an address the API does not answer on, so every attempt failed, and the reason came back as unreadable text instead of a message. Rebinding a key to a new site URL works now, and the result names the domain the key ended up on.
• Note: a rebind takes effect at once rather than waiting for approval. The API limits how often a key may move and emails the account owner each time.
• Housekeeping: the changelog below had lost its entries for 0.5.6, 0.5.7, 0.5.8, 0.7.5, 1.3.0, 1.4.0 and 1.5.0. All seven are restored.

1.5.1

• Fix: a birth time written with a single-digit hour, like 9:15, was silently ignored. On the synastry widget that meant the time was treated as unknown and the score was calculated for a different chart. Times like 24:00 and 09:60 were also being accepted and sent on as real.

1.5.0

• New: the synastry widget is rendered by your server into the page instead of loading in a frame, and still needs no key. The score, the word the API puts on it, and the aspects behind it as a table headed by the two names.
• New: name_a and name_b head the two columns. "Moon conjunct Mercury" says nothing until you know whose Moon. The names stay on your server; the API is not told them.
• New: aspects="12" shows more rows, up to twenty. Six by default, which is what the frame showed. The whole grid, points included, is behind a click either way.
• Better: a birth time you do not have is declared unknown rather than guessed at noon, which would move the Moon by up to six degrees and invent an aspect. The score and the cross-aspects survive it.
• Efficiency: the answer is cached for a month, the way a birth chart is. One synastry counts as three requests of the hourly allowance, because it is two charts and the grid between them.

1.4.0

• New: [astroway_yearly_horoscope sign="leo"], the year ahead for one sign.
• New: [astroway_zodiac_compatibility sign1="leo" sign2="aquarius"], how two signs read together. Prose rather than a percentage: the API returns no score, and a number with no calculation behind it is worse than no number.
• New: [astroway_chinese_zodiac date="1990-05-15"], the animal of a birth year with its element, polarity and pillar.
• New: tabs. Put several AstroWay blocks inside an Astrology Section and set its layout to Tabs. Your server still renders every card into the page; a 3 KB script folds the stack into a tab strip with arrow-key navigation, and with JavaScript off the page is the stack it always was.
• Better: cards now separate. A rule under every header, a rule above every section, and one framed table with a banded header row and striped body in place of an underline per row.
• Better: the row you are in, the current planetary hour or the open void of course window, is marked strongly enough to see when it lands on a striped row.
• Better: tables and field lists follow the reading direction, which matters in Arabic and Hebrew.
• Compatibility: the three endpoints above keep the shortcode and block names they had as generated ones in 1.2.0, so pages written then keep working and get the new card.

1.3.0

• New: is Mercury retrograde? [astroway_mercury_retrograde] answers yes or no with the dates of the retrograde it is in or heading for, and a countdown. [astroway_retrograde planet="saturn"] does the same for any of the eight planets that station.
• New: [astroway_retrogrades] puts all eight in one table, with the ones running backwards marked.
• New: [astroway_moon_voc] says whether the Moon is void of course right now and lists the windows around it, each with its last aspect and the sign the Moon enters next.
• New: [astroway_planetary_hours latitude="50.45" longitude="30.52"] prints the twenty-four planetary hours of the day with the hour you are in marked.
• New: daily transit alerts. Your site emails you on the days a planet stations or the Moon goes void of course, and stays quiet otherwise. AstroWay → Settings, Pro plan.
• Better: [astroway_moon_voc] and [astroway_planetary_hours] existed as generated shortcodes in 1.2.0 and printed a generic table. Same names, same attributes, purpose-built cards.
• Correct: every date and time in these cards is printed on your site's clock rather than in UTC. Saturn turns direct at 23:31 on 10 December, which is the 11th anywhere east of Greenwich.
• Efficiency: the single-planet card and the whole board ask the same question, so a page carrying both spends one request, and the answer is cached for a month while the reading is worked out fresh on every page view.

1.2.0

• New: a shortcode and a Gutenberg block for nearly every endpoint the API has, 682 of them across 49 families, generated from the API specification instead of written by hand. Vedic, numerology, tarot, BaZi, Zi Wei Dou Shu, Human Design, geomancy, runes, Mayan calendars, astrocartography, horary and more. They need an API key; the ten hand-built widgets still need nothing.
• New: AstroWay → Shortcodes lists them by family, each with a copy button, and the filter box searches all seven hundred.
• New: the generated blocks live in their own category in the inserter, so the hand-built ones stay where they were.
• Efficiency: a page pays for the endpoints it uses. The generated blocks are not registered on the front end at all; each renders on demand when it appears in the content.

1.1.0

• New: Human Design is rendered into the page. Type, strategy, authority, profile, definition, incarnation cross, the defined and open centres and the channels are now text your visitors can read and search engines can index, in place of the frame that held the same facts where neither could reach them.
• New: Moon Sign and Rising Sign, each answering one question on its own instead of burying it in a full chart. The rising sign card also names the chart ruler, where it sits, and the Midheaven.
• New: the Astrology Section block. Set a zodiac sign on it once and every AstroWay block inside follows, in the editor preview as well as on the page. A block with its own sign keeps it.
• Efficiency: the natal chart, moon sign and rising sign cards share one cached answer, so a page carrying all three costs one request instead of three.
• i18n: 45 new strings, translated in all 20 bundled locales.

1.0.4

• Fix: the block preview in the editor is styled again. WordPress draws the editor canvas in an iframe, which the plugin stylesheet never reached, so a horoscope card previewed as bare text while the published page showed it framed and spaced.

1.0.3

• Tested against WordPress 7.1: all sixteen blocks render inside the iframed post editor and on the front end, the inspector panels still draw their controls, and the settings screen is unchanged.
• Housekeeping: the minimum WordPress version now states 6.3, which is what the blocks have needed since they moved to block.json API version 3. The plugin name matches between the plugin header and this file.

1.0.2

• Fix: the city search on the settings screens now counts against your own site's hourly allowance instead of one shared with every site on the same server. On shared hosting a busy neighbour could use it up.
• Fix: when the city service is rate-limited the search reports how long to wait, instead of showing "upstream 429".
• i18n: the new message is translated in all 20 bundled locales.

1.0.1

• Fix: opening the AstroWay admin page could end in a fatal error ("Class AstroWay\WPPlugin\Updater not found") on sites that installed the plugin from wordpress.org. The update-channel card is now skipped on those builds, where it never applied.

1.0.0

• New: seven widgets are now rendered by your server into the page instead of being loaded in an embedded frame: daily, weekly and monthly horoscope, moon phase, Tarot card of the day (Rider-Waite), planet of the day, and the natal chart. Their text becomes part of your HTML, so search engines index it and screen readers announce it. Until now every widget lived in a frame, which is a separate document, and none of that content counted toward your page.
• New: the widgets inherit your theme. They are styled with currentColor rather than a palette of their own, so they read correctly in light and dark themes with no configuration on either side, and they collapse to a single column on narrow screens.
• New: three shortcodes that had templates but no way to reach them: [astroway_weekly_horoscope], [astroway_monthly_horoscope] and [astroway_planet_of_day].
• New: the natal chart card carries planet placements with sign, degree, house and retrograde marker, the Ascendant, the Midheaven and the major aspects, alongside the wheel it always drew. A failed request falls back to the bare wheel, which is what the widget showed before.
• New: [astroway_natal] accepts theme, which was previously reachable on other widgets but not this one. The wheel is an image drawn by the API and cannot read the page it lands on, so a dark wheel could end up inside a light card with no way to say otherwise. Values are dark (unchanged default), light and console.
• New: "Render mode" is back in Settings and this time something reads it. "On this page" is the default; "In an iframe" puts every widget that has a frame equivalent back into one. The weekly and monthly horoscopes are page-render only, because the API has no embed route behind them.
• Change: the markup of those seven widgets has changed. They are now wrapped in astroway-horoscope-card, astroway-moon-card, astroway-tarot-card, astroway-planet-card and astroway-natal-card elements rather than a frame. Custom CSS written against the old frame markup needs updating, or set Render mode to "In an iframe" to keep the old output.
• Change: page-rendered widgets are counted against your site's allowance of 300 requests an hour rather than each visitor's 30, because the request now comes from your server. Answers are cached until the data itself changes: a daily horoscope until midnight UTC, a weekly one until Monday, a monthly one until the first of the month, a chart for a month. A page carrying all twelve signs spends twelve requests a day, not twelve an hour.
• Change: failures are cached too, for 60 seconds, so an exhausted allowance is given a chance to recover instead of being hit again on every page load.
• Fix: the weekly and monthly endpoints return Markdown, and the previous build would have printed the asterisks literally. A small safe subset is now parsed, with escaping applied before any tag is inserted.
• Fix: readings in Ukrainian, Russian and other Cyrillic languages were cut in the middle of words. The text was split on line breaks with a pattern that, outside UTF-8 mode, also treats the second byte of the letter "х" as a line break, so "небесних тіл" came out as "небесни" followed by a line break and " тіл". Every pattern that touches the API's text now runs in UTF-8 mode.
• Fix: a bulleted list that the API puts directly after a sentence, with no blank line between them, is now a list. It used to be printed as one run-on paragraph with the hyphens still in it.
• Fix: two shortcodes on consecutive lines were wrapped in a single paragraph by WordPress, and a card cannot live inside a paragraph: the browser closed it early, leaving an empty bordered box with the widget's text spilled out below it. Paragraphs made up entirely of AstroWay shortcodes are now unwrapped. A sentence written around a widget is left as the author wrote it.
• Fix: a site whose API key was on a plan this build did not have in its list saw the upgrade prompt in place of every widget, including the ones that need no key at all. The plan above Pro bought less than no plan. A plan name the plugin does not recognise is now read as newer than this release rather than lower than anonymous.
• Fix: the rate-limit reading shown in the admin notice came from a separate probe request against the wrong bucket. Every render already returns the quota headers, so the notice now reports the bucket the widgets actually spend from.
• Fix: the moon phase name and the planet of the day printed the API's English identifier on every non-English site, because the JSON endpoints used to answer in English whatever language was asked for, unlike the embedded frames. The API now returns a translation of its own for those fields and the card prefers it, which is what makes lang="uk" on an English site come out Ukrainian throughout; a translation the plugin carries covers anything the API has not translated, including chart placements and answers cached before this release. Tarot card names and the planet's theme words are open-ended lists and remain English until the API translates them.
• Change: when a key is saved in Settings, your server now offers it on the calls it makes to render a widget, so they are counted against your plan instead of the anonymous per-site allowance. Frames are unaffected: that request is made by the visitor's browser, and putting a key in a URL that lands in your page's markup is not something the plugin will do.
• Fix: five places in the admin screens still quoted the old limit of "30 requests/hour per visitor IP", and the rate-limit notice went further and promised that visitors were unaffected. With server-side rendering they are: the widgets fall back to a frame when the site's allowance runs out. All five now describe both buckets.
• New: the plugin's first admin screen is now "Getting started" rather than "API Key". It opens with three steps and a copyable shortcode, because nothing in the plugin needs a key; the key form is still on the same page, below them.
• New: three shortcodes for embed routes the API has had all along and the plugin never exposed: [astroway_mini_chart] (the natal wheel drawn small, for a sidebar), [astroway_monthly_forecast] (four weeks ahead for one sign) and [astroway_transit_timeline] (the next seven days of Moon ingresses).
• New: six Gutenberg blocks, so all 16 widgets are now both a shortcode and a block: Weekly Horoscope, Monthly Horoscope, Planet of the Day, Mini Birth Chart, Monthly Forecast and Moon Transit Timeline. The first three render into the page; the readme used to say they were "shortcodes for now".
• New: the shortcode reference lists all 16 shortcodes and has a search box. Kundli, Transit Sky, Panchang, Numerology and Synastry worked all along but appeared nowhere in the admin, so the only way to find them was the source. Their block names are corrected too: the reference named blocks that do not exist under those names in the inserter.
• Fix: the "What you get" comparison on the API Key page claimed a paid plan unlocks native rendering, Tarot, Human Design, Synastry and Numerology, and removes the watermark. None of that is true of the plugin: every shortcode works on the anonymous tier, page rendering is not gated, and the key never reaches the frame, so it cannot remove a watermark. The table now compares what a key actually changes, and says plainly that the widgets on your pages are unaffected by it.
• i18n: 63 new strings (signs, planets, aspects, houses, moon phases, settings) translated into all 20 bundled locales. Zodiac names got a second pass: the generic translator had left "Leo" in English in eleven of them and had rendered "Cancer" as the illness in Czech, Japanese, Korean, Turkish, Romanian, Indonesian and Dutch.
• i18n: 70 more strings for the new screens, and every remaining em-dash removed from translatable text (19 strings, including the ten synastry field labels in the block editor).

0.10.7

• Fix: widgets no longer disappear from your pages. The plugin probed its own server's rate limit and, when that quota ran out, rendered nothing at all, even though each visitor has a separate quota. Rendering no longer depends on that probe, and the probe now runs only where its reading is meaningful: the admin notice.
• Fix: [astroway_today_in_sky] and [astroway_fortune_cookie] are deprecated. The api routes they call were never implemented, so both rendered an empty frame. Pages containing them stay intact and administrators see a short note; the shortcodes will return when the routes exist.
• Fix: the activation, review and rate-limit notices appeared on every admin page, including other plugins' settings screens, while being hidden on our own. Both halves fixed: they show up on AstroWay screens only, and they are visible there.
• Fix: the "Render mode" and "Spend cap" settings were saved but never read by anything. Both panels are removed until they actually do something.
• Change: wp.org builds no longer bundle an update checker, per directory rules. Updates come from wordpress.org as before.
• New: five Gutenberg blocks with matching shortcodes, each rendering an anonymous embed: Vedic Kundli, Transit Sky, Daily Panchang, Numerology and Synastry. The plugin now ships ten blocks.
• Fix: Natal Chart and Bodygraph sent longitude as lon (the api reads lng) and the timezone as a name rather than a numeric offset, so charts were built for longitude 0 and UTC. House cusps and the Ascendant are now correct. No content edits needed.
• Fix: verifying a rejected API key showed an empty success panel instead of the rejection reason.
• New: optional "Widget disclaimer" setting, off by default, appends a short informational line to embedded widgets.
• New: the admin menu carries the AstroWay owl mark.
• Note: the review prompt and the rate-limit notice announced in 0.5.6 were missing from the published builds until now. They ship with this release.

0.10.6

• New: "Widget disclaimer" setting (Settings → AstroWay). Off by default. When enabled, embedded widgets show a short "informational, not professional advice" line in their footer, useful when your jurisdiction or compliance policy requires it. The wording is rendered and localized by api.astroway.info.
• Fix: the "Spend cap" field on the Settings page no longer renders as an oversized box (it had inherited a flex value meant for horizontal layouts).

0.10.5

• Branding: the admin menu icon and the review-prompt now use the AstroWay owl mark instead of a generic star.
• Fix: verifying a rejected API key now shows a clear error message instead of an empty green panel (the panel only appeared blank because the request still reported success on a 401).

0.10.4

• New: 5 Gutenberg blocks + matching shortcodes, Vedic Kundli, Transit Sky, Daily Panchang, Numerology, and Synastry compatibility. Each wraps a /v1/embed/* endpoint as an anonymous-friendly responsive iframe. Plugin now ships 10 blocks.
• New: dark / light / console theme selector on the new widgets.
• Fix: Natal Chart and Bodygraph now send longitude as lng and the timezone as a numeric UTC offset. The api had been receiving longitude 0 and UTC, so house cusps and the Ascendant were computed for the wrong location/time, charts are now correct. Existing blocks need no changes; just upgrade.

0.10.3

• Two final Elementor widgets: AstroWay Today in Sky (with SWITCHER controls for Sun/Moon, Mercury retrograde, planetary hour, location fields conditional) + AstroWay Fortune Cookie (optional sign dropdown).
• Closes Elementor wrapper stack (v0.10.0-v0.10.3). Plugin now ships 7 Elementor widgets covering all 7 core shortcodes.

0.10.2

• Two more Elementor widgets: AstroWay Human Design Bodygraph + AstroWay Daily Tarot (with deck dropdown, Rider-Waite/Marseille/Lenormand).

0.10.1

• Two more Elementor widgets: AstroWay Daily Horoscope (sign dropdown) + AstroWay Moon Phase (date + lang). Same render-via-shortcode pattern as v0.10.0.

0.10.0

• New AstroWay category in Elementor widget panel. First widget: AstroWay Natal Chart, which wraps the [astroway_natal] shortcode with Inspector controls for date/time/lat/lon/tz/lang. Loads only when Elementor plugin is active.
• First piece of Elementor integration stack (v0.10.0-v0.10.3). Standalone astroway-elementor addon plugin (planned ~Aug 2026) will provide advanced controls + animations.

0.9.4

• New shortcode [astroway_fortune_cookie] shows a daily AI-generated cosmic quote via /v1/embed/fortune-cookie. Anonymous-accessible, sign-aware (optional sign param).
• Closes Today in Sky stack (v0.9.0-v0.9.4).

0.9.3

• [astroway_today_in_sky] accepts show_planetary_hour (default 0) + lat, lon, tz parameters. When enabled, the widget pulls today's planetary hour mapping for the supplied location.

0.9.2

• [astroway_today_in_sky] accepts show_retrograde parameter (default 1), toggles the Mercury retrograde indicator section. SEO-friendly viral content for retrograde periods.

0.9.1

• [astroway_today_in_sky] accepts show_signs parameter (default 1): toggles the Sun/Moon zodiac positions block. New sanitize_bool_flag() helper added as public static for addon reuse.

0.9.0

• New shortcode [astroway_today_in_sky] renders the day's celestial overview via /v1/embed/today-in-sky. Anonymous-accessible (IP-rate-limited iframe).
• New widget config in RendererDecisions registry; new feature key in Tier::matrix. Sub-features (sun/moon positions, retrogrades, planetary hour, Fortune Cookie) land in v0.9.1-v0.9.4.

0.8.3

• New Settings panel "Domain binding": shows current domain attached to the key + input to request rebinding via POST /v1/auth/keys/domain-change. Manual fallback link to api dashboard if the endpoint returns an error.
• Closes admin enhancements stack (v0.8.0-v0.8.3).

0.8.2

• New Settings panel "Feature matrix": visual grid of features × tiers with checkmarks. Highlights the current tier's column. Reads from Tier::matrix() so addon-registered features appear automatically.

0.8.1

• New Settings panel "Spend cap": local mirror of the monthly USD ceiling configurable at api.astroway.info/dashboard/billing. Stored as integer 0..100000 in OPTION_KEY['spend_cap_usd'].

0.8.0

• New Settings panel "Render mode" with radio toggle: Auto (default) / Force iframe / Force client. Stored in OPTION_KEY['render_mode']. RendererDecisions wiring lands when native client widgets ship in v1.1+.
• First piece of admin enhancements stack (v0.8.0-v0.8.3).

0.7.5

• Per-shortcode tier guards: each core astroway_* shortcode is now wrapped with Tier::can( $feature ). Locked shortcodes render an inline "Pro feature" CTA. Behavior matches v0.7.2 block-side gating - v1 shortcodes remain anonymous-accessible.

0.7.4

• New Tier::render_upgrade_cta( $feature ) returns a styled CTA panel with feature label + upgrade button linking to api.astroway.info/dashboard/upgrade. Filterable via astroway_upgrade_cta_html for theme/addon customization.
• Block + shortcode guards (v0.7.2/v0.7.3) refactored to call the helper. Closes the v0.7.x tier-gating stack and pre-v1.0 blocker B3.

0.7.3

• Per-shortcode tier guards: each core astroway_* shortcode is now wrapped with Tier::can( $feature ). Locked shortcodes render an inline "Pro feature" CTA. Behavior matches v0.7.2 block-side gating, v1 shortcodes remain anonymous-accessible.

0.7.2

• Per-block tier guards: each registered Gutenberg block is now wrapped with Tier::can( $feature ). Locked blocks render an inline "Pro feature" CTA instead of the widget. All v1 blocks remain accessible to anonymous users (matrix default); guards activate for v1.x+ Pro blocks.

0.7.1

• New Tier::can( string $feature ): bool checks whether current tier can access a feature.
• New Tier::matrix(): array returns feature → allowed tiers map, filterable via astroway_tier_matrix so addons can declare their own features.
• Default matrix: v1 widgets (natal, daily_horoscope, moon_phase, bodygraph, daily_tarot) anonymous-OK; synastry/solar_return/lunar_return/progressions/native_render paid-only; ai_chat/transit_alerts pro+.

0.7.0

• New utility class AstroWay\WPPlugin\Tier with Tier::current() resolving the user's plan from cached /v1/auth/keys/me response (30 min TTL). Returns anonymous/free/indie/starter/pro/business/internal.
• AddonAPI::current_tier() refactored as facade delegating to Tier::current(). First piece of tier-gating subsystem (v0.7.x).

0.6.5

• New developer guide docs/addon-development.md documents the v0.6.x Addon Hooks API + AddonAPI reference + minimal working example.
• New example addon scaffold docs/example-addon/ shows shortcode registration + tier check + widget declaration.
• Closes the Addon Hooks API atomic stack v0.6.0-v0.6.5. Track 3 addon plugins can now develop against a stable surface.

0.6.4

• New public class AstroWay\WPPlugin\AddonAPI: BC-locked stable surface for addon developers. Methods: register_widget(), current_tier(), api_base(), has_key(), cache_key(). Internal classes (RendererDecisions, ApiClient, Cache, Admin) remain unstable.

0.6.3

• New filter: astroway_widgets lets addons append entries to the widget registry without touching core. Useful for new shortcodes/blocks that map to api /v1/embed/* endpoints.

0.6.2

• New action: astroway_register_blocks fires at end of Blocks::register_assets_and_blocks(). Addons hook here to call register_block_type() for their own astroway/* Gutenberg blocks.

0.6.1

• New action: astroway_register_shortcodes fires at end of Shortcodes::register(). Addons hook here to call add_shortcode() for their own astroway_* shortcodes.

0.6.0

• New action: astroway_init fires early in plugin boot, signalling addons that core classes are loaded and they can hook into upcoming registration actions.
• First atomic piece of the Addon Hooks API (v0.6.0-v0.6.5). Unlocks third-party addon ecosystem.

0.5.8

• Follow-up hotfix on v0.5.7: also guards require_once for class-updater.php and class_exists() checks around Updater::boot() / Elementor\Loader::boot(). All forward-version dependencies in the main plugin file and Plugin::boot() now degrade gracefully if the corresponding includes/ files aren't bundled in the current ZIP.

0.5.7

• Hotfix on top of v0.5.6: the main plugin file required class-tier.php / class-addon-api.php / elementor.php unconditionally, but those classes only ship in later versions and were missing from the v0.5.6 ZIP - every page load fatal-erred. Those three require_once calls are now guarded by file_exists() so older ZIPs load cleanly. Also wraps Tier::current() in class_exists() for the same reason.
• No behavior change for v0.5.6 features (review prompt + anonymous rate-limit guard) - they keep working as designed.

0.5.6

• Added a one-time review prompt in WP admin shown 14 days after activation, dismissible per-user.
• Anonymous rate-limit guard: when the api responds that the public 30/h-per-IP limit is exhausted, the plugin now skips rendering the iframe (no more raw JSON error visible to visitors) and surfaces a one-time admin notice pointing the site owner at a free API key. Paid tiers and any configured API key skip the probe entirely. The probe itself is cached for 5 minutes in a transient so it adds at most one extra api hit per site every five minutes.

0.5.5

• Admin: new "Update channel" panel on the API Key page shows current channel (A/B), whether PUC library is loaded, whether an API key is set, and last update check timestamp.
• Closes the Channel B atomic stack v0.5.0-v0.5.5. Plugin meets the v1.0 "Channel B custom updater" stability gate condition.

0.5.4

• Channel B update checks now send Cache-Control: no-cache + Pragma: no-cache headers, ensuring fresh response from astroway.info even if a transit cache sits between WP and the server.
• "View details" modal verified to render correctly with PUC defaults: pulls changelog/sections from update.json.

0.5.3

• Channel B custom updater wired via plugin-update-checker: registers against https://astroway.info/wp-plugin/update.json with the saved API key carried as ?key= query arg.
• When PUC is absent or the server endpoint is unreachable, wp.org Channel A continues to deliver updates as before.

0.5.2

• Bundled YahnisElsts/plugin-update-checker v5.6 library at includes/lib/plugin-update-checker/, autoloaded via load-v5p6.php. Foundation for v0.5.3 Channel B update hook.
• No new user-visible behavior. PUC is loaded but no update checker instance is created yet.

0.5.1

• Channel B download endpoint live at astroway.info/wp-plugin/download/{version}/, 302-redirects paid-tier keys to versioned ZIP on GitHub Releases.
• update.json now returns full download_url field for paid tiers.
• No user-visible plugin code change. Plugin-side update hooks land in v0.5.3.

0.5.0

• Channel B server endpoint deployed at astroway.info/wp-plugin/update.json, paid-tier auto-update infrastructure (first of 6 atomic pieces, v0.5.0-v0.5.5).
• No user-visible plugin code change. Plugin-side updater hooks land in v0.5.3.

0.4.0

• CI/Tests infrastructure: PHPUnit unit tests + WPCS lint via GitHub Actions matrix (PHP 8.1-8.4 full test, 7.4/8.0 syntax compat)
• Refactor: input sanitization extracted as public statics on Shortcodes class (no behavior change, enables addon reuse)
• No user-visible changes: pure foundation for upcoming addon ecosystem (v0.6.0)

0.3.0

• New: live Status panel on the API Key admin landing, plan / credits / period / domain pulled from /v1/auth/keys/me (30 min transient cache)
• New: lang attribute on all 5 shortcodes (e.g. [astroway_natal date="..." lang="ru"]), 21 api-supported locales
• New: Language Inspector dropdown on all 5 Gutenberg blocks, uk, en, de, ru, pl, es, pt, fr, it, nl, cs, ro, hu, el, tr, ar, hi, ja, ko, vi, id
• Default lang resolves to the WP site locale; invalid codes silently fall back, no user-facing error
• Status panel handles all 5 states: valid / suspended / revoked / invalid_key / api_down with per-state color accent
• Requires api.astroway.info v2.33.0+ for /v1/auth/keys/me; falls back to legacy /v1/keys/usage with "Limited data" notice on older self-hosted api
• No regressions on v0.2.3: existing shortcodes/blocks without lang= render in site default exactly as before

0.2.3

• All 3 subpages share one hero (brand + status badge + CTAs); only title and tagline vary per page
• Right sidebar restored (Resources + System + quote) in a 1fr + 280px grid
• Buttons read as buttons in both light panels and the dark hero (ghost variant + on-dark override)
• Shortcode reference cards gain proper panel-body inset
• New: city → lat/lon/IANA-tz helper on the Shortcodes page (server-side proxy to app.astroway.info atlas + click-to-copy snippet)
• Type tokens drop bundled webfont declarations: pure ui-sans-serif/system-ui stack, multi-script coverage via OS fonts
• 20 bundled translations: uk, de_DE, ru_RU, pl_PL, es_ES, pt_BR, hi_IN, fr_FR, ko_KR, it_IT, ja, id_ID, tr_TR, nl_NL, ro_RO, cs_CZ, vi, ar (RTL), el, hu_HU
• Translation filenames corrected to {textdomain}-{locale}.mo + explicit load_plugin_textdomain call

0.2.2

• Admin UI split into 3 submenu pages: API Key (default landing), Settings, Shortcodes
• API Key landing rebuilt with 3-tier comparison (Anonymous / Free key / Paid), state badge, key form, prominent CTAs
• Settings page focused on diagnostics: Connection ping, Cache stats + purge, System info with Copy diagnostic button
• Shortcodes page rebuilt as expanded reference cards (description + copyable code + params table + Gutenberg block hint per shortcode)
• JS split per-page (api-key / settings / shortcodes), reducing payload on each admin screen

0.2.1

• Settings page promoted to a top-level admin menu item with a custom brand icon (star inside orbit ring, single-path SVG)
• Activation notice rebranded with a cosmic-gradient mark, two CTAs (Get free API key / Open Settings), and persistent dismiss (fix for a latent bug where the dismiss action did not survive page reloads)
• Settings page fully redesigned with an observatory aesthetic: hero with owl-moon logo, four numbered panels (API key / Connection / Cache / Shortcodes), right-side Resources / System / quote aside, paper-warm cards with gold hairlines
• Shortcode rows copy-to-clipboard on click
• ASTROWAY_WP_PLUGIN_VERSION constant auto-derived from the plugin header via get_file_data, single source of truth, simpler release pipeline

0.2.0

• Settings page under Settings → AstroWay (API key input, Verify Key, Test Connection, Cache controls, shortcode reference, Diagnostics)
• API key field accepts both sandbox (aw_test_) and live (aw_live_) keys
• All keyed requests now carry X-Api-Key + X-AstroWay-Site-URL headers (lazy domain bind support)
• Plugin row links: Settings + Get API Key (with ?source=wp_plugin)
• Activation notice CTA URL includes ?source=wp_plugin for referrer-source tracking
• New transient cache layer (prefix astroway_v1_) with purge button + stats
• Verify Key gracefully falls back to /v1/keys/usage until api ships /v1/auth/keys/me (Block A)

0.1.0

• MVP: 5 iframe shortcodes via /v1/embed/* (works without API key, 30/hr per IP)
• 5 Gutenberg blocks with ServerSideRender
• Vanilla CSS theme-overridable via CSS vars (--astroway-*)
• i18n .pot + EN/UK/DE/PL base translations
• Graceful 429 handler with 'Get free API key' admin notice

0.1.0-alpha.1

• Initial scaffold (pre-release). Plugin header + PSR-4 autoload + activation hooks. No shortcodes yet, first functional release planned as 0.1.0.