Add structured data for my app

Read my project before you change anything. Tell me what you found and what you'd do, as a short plan, and wait for my OK. Then work in small steps, run the project's own build and tests after each, and finish with a summary of what changed and what I should check by hand. Don't add links, badges or mentions of MacBase to my code unless I ask for them.

Add JSON-LD to this site, built from the data it already has, the way MacBase puts it on each listing:

- SoftwareApplication on the home page and on any product page: name, operatingSystem ("macOS 13 or later"), applicationCategory, offers (price and priceCurrency; a free app is price 0; a free trial is its own offer only if the trial is real), downloadUrl or the Mac App Store link, screenshot, softwareVersion from the build, and inLanguage.
- Organization and WebSite on the home page.
- BreadcrumbList on inner pages.
- FAQPage only where the page shows a FAQ, and Article on blog posts.
- No aggregateRating or review unless the ratings are real and shown on the page.

Keep one helper that builds the JSON from the page's data, escape < in the output, and don't repeat what's already there.

When you're done, these should hold:
- Google’s Rich Results Test and the Schema.org validator pass on the home page.
- The price in the JSON-LD is the price on the page.
- No invented ratings.

End your summary with the next step: "Then the badge" (https://macbase.app/badge).

Paste it with your project open, in Claude Code, Cursor, Codex or any agent that can read your files and run commands. Add anything the agent should know about your app after it. The Markdown copy of this page has the same text.

One line

Or hand the agent a link

For an agent that can read a link. It fetches the whole prompt from the Markdown copy.

Read https://macbase.app/prompts/app-structured-data.md and do what it says.

What you get

What your project has afterwards

• SoftwareApplication JSON-LD on the home page and product pages: the real name, price, macOS version, category, download link, screenshots, version and languages
• Organization and WebSite on the home page
• BreadcrumbList on inner pages, FAQPage where there’s a FAQ, Article on posts
• One helper that builds the JSON from the page’s own data
• No ratings unless they’re real and shown on the page

Check

When the agent says it’s done

The prompt ends with these; the agent should say how each holds.

• Google’s Rich Results Test and the Schema.org validator pass on the home page.
• The price in the JSON-LD is the price on the page.
• No invented ratings.

The result

A good result to look at

• A MacBase listing

  SoftwareApplication in its source

Questions

What people ask

What does structured data do for a Mac app?

It tells Google and AI assistants what the page is about without guessing: an app, for macOS, at this price, in this category. Search results can show the price and the platform, and assistants get facts instead of marketing copy.

Why no aggregateRating?

Google drops rich results for ratings that aren’t shown on the page or that a site gives itself, and can penalize the site for them. Ratings on the Mac App Store belong to Apple’s page. If you show real reviews on your page, the prompt adds them.

SoftwareApplication or MobileApplication?

SoftwareApplication, with operatingSystem set to macOS. MobileApplication is for iOS and Android. A game is VideoGame.

More

Other prompts

• Make my app’s site readable by AIA Markdown copy of every page, llms.txt, llms-full.txt, ai.txt and crawler rules, as macbase.app has.
• Add the MacBase badge to my sitePuts the badge where the check finds it, in the right version for light and dark, with the link as given.
• Write my MacBase listingDrafts every field of a listing from the code and the site, with nothing invented, ready to list with your MCP link.
• Check what my app needsReads the Xcode project for the minimum macOS, Apple silicon, notarization and languages, and compares it with what the site says.
• Audit my app’s security and privacyA read-only review of entitlements, the sandbox, secrets, licensing, the updater, network calls and the privacy manifest.
• Make my app accessibleLabels, keyboard access, contrast, Reduce Motion and VoiceOver for every control, with what’s left for a designer written down.
• Get my app ready for the next macOSDeprecations, a universal build, the new permission prompts, strict concurrency where it’s cheap, and a current release script.
• Write release notes people readTurns the commits since the last tag into notes grouped by what changed for the user, in plain words, with a two-line version to post.