If you've already marked up your business with LocalBusiness and Organization schema, you've done the part that matters most — and you've also reached the point where most guidance stops being useful. What comes next is genuinely harder, because the honest answer to "what else should I add?" involves knowing which schema types still earn anything, which quietly do nothing, and which Google retired while you weren't looking. That list changed significantly in 2026. Here's where the effort actually pays off now, for a Dominican business that's past the basics.

First: what changed in 2026

This matters before anything else, because effort spent on retired features is wasted entirely.

The biggest change: FAQ rich results are gone. After progressively restricting them, Google fully removed FAQ rich results in May 2026, and is retiring the corresponding Search Console report — meaning FAQPage markup no longer produces the expandable question list in search results for any ordinary business. HowTo rich results were removed back in 2023 and remain gone. A batch of other types — including Course Info, Claim Review, Estimated Salary, Special Announcement, and Vehicle Listing — were also retired.

Two consequences. First, if a developer or plugin is still adding FAQPage or HowTo markup expecting rich results, that's now decorative. Second — and this is the nuance worth holding — the markup isn't harmful, and clear question-and-answer structure still helps AI systems extract your content, which matters increasingly for how businesses show up in ChatGPT and Google's AI answers. Just don't expect a visible search feature from it.

The types worth your effort now

Beyond LocalBusiness and Organization, these are the ones that still do real work for Dominican businesses:

• Product and Offer — for anyone selling online. Price, availability, and review data can appear directly in results, and Google now supports organization-level shipping and return policy markup so you don't repeat it on every product. If you run a store, this is the highest-return schema type available to you.

• Vacation rental — genuinely new and directly relevant here. Google's supported gallery now includes a vacation rental type, which for a Dominican villa, apartment, or short-term rental business is a rare opportunity: a purpose-built schema for exactly what you sell, in a market where almost no local competitor will implement it.

• Event — for venues, tour operators, bars, and anyone running dated activities. Dates, locations, and ticketing can appear as grouped results, and it's chronically underused by Dominican businesses running regular events.

• VideoObject — if you produce video, this makes it eligible for video results and thumbnails. Hotels, tour operators, and photographers with real video content leave this on the table constantly.

• JobPosting — if you hire, your vacancies can appear in Google's job search experience.

• Review snippet — still one of the most visible features there is, and still active. But it must reflect genuine reviews of the item on the page; inventing or importing ratings is the fastest route to a manual penalty.

• Breadcrumb — still supported on desktop and still worth having, though it lost mobile display in 2025.

The principle that decides everything

Here's the rule that resolves most implementation questions: schema must describe what a human can actually see on the page. Markup claiming an event, a price, or a rating that a visitor can't find in the visible content is a violation, and Google issues manual actions for it. This is where most well-intentioned implementations go wrong — a developer adds aggregate ratings sitewide, or Product markup on a page that isn't a product, and either it silently does nothing or it earns a penalty.

The corollary is that schema is not a shortcut. It doesn't lift rankings — Google has said so repeatedly — and it can't compensate for a page with nothing on it. What it does is make an already-good page eligible for a more prominent, more clickable result. That's genuinely valuable, but only on top of real content.

Completeness, not presence

The second thing that separates working schema from decorative schema: partial implementation produces nothing. A Product without the required properties won't generate a rich result. An Article missing its author won't display attribution. There's no partial credit — you either meet the requirements for a feature or you don't appear, and a great many sites carry markup that has never once produced anything because one required field is absent.

This is why testing matters more than adding. Google's Rich Results Test tells you whether a page is actually eligible for a feature, and Search Console's reports show errors across your whole site. If you've added schema and never checked either, you genuinely don't know whether any of it works — and the odds are that some of it doesn't.

Combining types without making a mess

Real pages usually deserve several types at once, and this is where implementations get tangled. A tour operator's excursion page might reasonably carry Organization for the business, Product or Offer for the excursion, Breadcrumb for its position in the site, and Review if genuine reviews are displayed. A hotel page might carry LocalBusiness, vacation rental markup, and Review.

The clean approach is a single JSON-LD block per page containing the connected entities, rather than several disconnected blocks that repeat and contradict each other. The common failure is duplication — a theme adding Organization markup, a plugin adding it again with different details, and a developer adding a third version. Conflicting information is worse than none, because you're telling Google two different things about the same business and it has to guess which to trust.

Keeping it accurate over time

The failure nobody plans for: schema goes stale. Your hours change for the season and the markup still says the old ones. A price rises and the Product data doesn't. An event passes and the Event markup sits there advertising it. Structured data that contradicts reality is worse than no structured data, because it produces a search result that misleads a customer — who arrives annoyed, or doesn't arrive at all.

Treat markup as part of routine maintenance rather than a one-time task, and prefer implementations that generate schema automatically from your actual content — so when you update your hours or prices in one place, the markup updates with them. That's the difference between a system and a liability.

Where to actually start, by business type

To make this concrete rather than abstract, the two or three types worth implementing depend entirely on what you sell. A hotel, villa, or short-term rental should look at LocalBusiness plus the vacation rental type and Review. A restaurant wants LocalBusiness with accurate hours, plus Menu markup and Review. A tour operator benefits most from Product or Offer on each excursion page, plus Event for anything with fixed dates. An online store should focus entirely on Product and Offer with complete required fields, plus the organization-level shipping and return policy markup. A clinic, law firm, or professional practice wants LocalBusiness, Organization, and Person markup for named practitioners. A photographer or agency should consider VideoObject if there's real video, plus Breadcrumb and Review.

That's the whole recommendation. Three types implemented completely and kept accurate outperform ten added carelessly — and this shortlist is more useful than any exhaustive catalogue, because it's the subset that matches what Dominican businesses actually sell.

An honest word on how much this matters

Perspective, because schema attracts more enthusiasm than it deserves. Structured data will not rescue a slow site, rank a thin page, or substitute for the fundamentals — good content, speed, a genuinely bilingual structure, and a complete Google Business Profile all matter more. Its value is real but bounded: it makes an already-competitive result more prominent and more clickable, and it makes your content easier for machines — including AI systems — to read correctly.

So the honest priority order for a Dominican business is: get the basics right, then add the two or three types that genuinely match what you sell, implement them completely, test them, and keep them accurate. That beats a sprawling implementation of a dozen types where half are retired and none are complete.

Structured data that actually earns something

At DR Web Studio we generate structured data from your real content — so it's complete, accurate, and updates when your site does — and we implement the types that still earn results rather than the ones that stopped working. If you have schema on your site and no idea whether any of it is doing anything, contact us for a free consultation and we'll test it and tell you honestly what's working, what's retired, and what's worth adding.