SEO & AEO Intelligence Report — viverehotel.com.ph

📊 Executive Summary

The headline: Vivere Hotel is a 25-year-old landmark property with strong brand recognition in Alabang — but the website is virtually invisible to both Google rich results and AI answer engines. Zero Hotel schema, multiple H1 tags on every page, 80%+ images missing alt text, and a 92-question FAQ page with no structured data. The brand’s real-world reputation is not translating to digital authority. Meanwhile, competitors like Acacia, The Bellevue, and Azumi are eating your SERP share with schema, reviews, and content that AI engines can actually parse.

187

URLs in Sitemap

Pages with Hotel Schema

~80%

Images Missing Alt Text

7 / 13

Pages with Multiple H1s

FAQs with No Schema

3 / 8

AEO Citation Tests Passed

PageSpeed Insights / Lighthouse Scores (verified May 8, 2026)

Mobile Performance

100

Mobile Accessibility

Mobile Best Practices

100

Mobile SEO

Desktop Performance

Desktop Accessibility

100

Desktop Best Practices

100

Desktop SEO

Lighthouse context: SEO 100 and Accessibility 100 from Lighthouse are technical pass/fail checks (meta viewport exists, title exists, robots not blocked, color contrast, ARIA labels). They do NOT assess title tag quality, keyword targeting, schema richness, or deep alt-text coverage — which is why our manual audit scores are lower. Mobile Performance at 63 confirms the 251 KB HTML + 30 CSS files issue flagged in Finding #10. Desktop at 95 shows the infrastructure (Cloudflare, WP Rocket, HTTP/2) handles desktop well.

Top Wins

Lighthouse SEO 100 + Accessibility 100 (mobile) — Technical SEO foundations pass all automated checks. Strong baseline to build on.
llms.txt exists — Yoast-generated structured content file for LLM consumption. Rare for Philippine hotels. Positive AEO signal.
The Nest rooftop content ranks — Blog post at /stories/the-nest-rooftop-dining-alabang-manila/ is a textbook AEO asset: cited by AI engines for “rooftop bar Alabang” queries.
Event/wedding pages perform — /venues/ and /alabang-wedding-venue/ rank well with extractable capacity data (12 venues, 300 guests).
Strong security & infrastructure — Cloudflare CDN, HTTPS with HSTS, HTTP/2 + HTTP/3, proper security headers, WP Rocket caching, locally-served fonts. Desktop Performance 95.

Biggest Issues Holding the Site Back

Zero Hotel/LodgingBusiness schema — The site has no structured data telling Google or AI engines this is a hotel. No star rating, no room types, no price range, no amenities in machine-readable format.
Multiple H1 tags on 54% of pages — Homepage has 3 H1s. Stay, Dine, Meet, Gallery, and Celebrate pages each have 2. Confuses search engine heading hierarchy.
~80% of images missing alt text — Gallery page: 20 images, 0 alt. Stay page: 13 images, 0 alt. Dine: 8 images, 0 alt. Massive accessibility and SEO gap.
92 FAQs with zero FAQPage schema — The FAQ page is the single biggest quick win on the site. Adding structured data would immediately generate rich results.
OTAs dominate branded and non-branded SERPs — For 5 of 8 test queries, OTAs (Booking.com, Expedia, Agoda) own the results. No Vivere content breaks through.

🎯 Scorecard — Pillar Performance

On-Page SEO

4.0

Schema / AEO Readiness

2.0

Technical SEO

6.0

Content Depth & Quality

5.0

Local SEO

3.0

E-E-A-T / Trust Signals

4.5

AI Search / AEO Visibility

3.5

Image & Media SEO

2.0

On-Page SEO — 4.0/10

7 of 13 audited primary pages have multiple H1 tags. H1s are generic single words (“Stay,” “Dine,” “Meet”) with no target keywords. Homepage title tag (55 chars) is acceptable, but inner-page meta descriptions are weak or absent. H2 hierarchy is inconsistent — “25 years” and “#viveremoments” used as H2s alongside semantic headings. Internal linking from homepage to key pages is present via navigation and body links, which is a modest positive.

Schema / AEO Readiness — 2.0/10

Homepage has minimal Yoast-generated schema (WebPage, Organization, BreadcrumbList, SearchAction) — but no Hotel, LodgingBusiness, LocalBusiness, FAQPage, Restaurant, EventVenue, Review, or AggregateRating schema anywhere on the site. The Organization schema has an empty description field and only lists Facebook + Instagram in sameAs (missing TripAdvisor, Google Business). The one bright spot: llms.txt exists, which is ahead of virtually every competitor in the market. Score held above 1.0 for that reason.

Technical SEO — 6.0/10

Strong infrastructure: Cloudflare CDN with HTTP/2+3, HTTPS with HSTS, proper security headers, WP Rocket caching, deferred JS, WebP delivery, locally-served fonts. Lighthouse verified: Desktop Performance 95, Mobile SEO 100, Best Practices 96/100. Deductions: Mobile Performance only 63 (251 KB HTML + 30 CSS files). robots.txt www mismatch. Malformed URL in story-sitemap. Cache-Control: max-age=0 means no CDN edge caching. Duplicate content paths (/stay/ vs /rooms/, /stories/ vs /blog/).

Content Depth & Quality — 5.0/10

Homepage has strong content (~1,200 words). FAQ page is excellent (92 questions, ~2,800 words across 10 categories). Recent Stories content (2026) shows investment in AEO-style articles. Deductions: Gallery (250 words), Dine (450 words), and Contact (450 words) are thin. 107 legacy blog posts from 2018–2020 are stale/dated COVID-era content. Two separate content hubs (/stories/ and /blog/) create fragmentation. Specials and venue pages lack descriptive depth beyond basic details.

Local SEO — 3.0/10

No LocalBusiness schema with address, phone, geo coordinates, or opening hours. No structured NAP (Name, Address, Phone) data for search engines. Address and phone appear in the footer visually, but not in machine-readable format. Google Maps links to nearby attractions are present (positive for users, neutral for SEO). No evidence of Google Business Profile optimization signals on the site (reviews widget, GBP link). Organization sameAs is limited to Facebook + Instagram.

E-E-A-T / Trust Signals — 4.5/10

25 years in business is a strong authority signal — when it surfaces. DOT accreditation and NPC DPA compliance badges shown on FAQ and Contact pages. Press releases mention Travel + Leisure awards. TripAdvisor presence exists. Deductions: no AggregateRating schema pulling review scores into SERPs. A negative TripAdvisor review titled “The worst hotel in Alabang” appears on page 1 of branded search — no reputation management strategy visible. No author attribution on blog/story content. No structured trust signals (awards, certifications) in schema.

AI Search / AEO Visibility — 3.5/10

3 of 8 test queries returned Vivere citations. The Nest rooftop content and event/wedding pages are strong AEO assets. llms.txt exists (rare competitive advantage). Deductions: 5 of 8 queries returned zero Vivere presence. OTAs dominate all generic hotel queries. No “business hotel,” “luxury hotel Alabang,” or “south of Manila” content exists. Competitor Acacia has structured review data (8.7/10, 2,059 reviews) that AI engines preferentially cite.

Image & Media SEO — 2.0/10

An estimated 80%+ of site images lack alt text. Gallery page: 20 images, 0 alt. Stay page: 13 images, 0 alt. Dine page: 8 images, 0 alt. Specials: 9 images, 0 alt. This is a site-wide failure in accessibility and image SEO. Positives: hero image is properly preloaded as WebP with fetchpriority=high. Fonts are served locally as WOFF2 (no external Google Fonts dependency). Lazy loading is implemented via WP Rocket.

🚨 Critical Issues

Critical #1: Zero Hotel / LodgingBusiness Schema

viverehotel.com.ph has no structured data telling search engines or AI answer engines that this is a hotel. No star rating, no room types, no amenities, no check-in/check-out times, no geo coordinates, no price range, no review aggregation — nothing. The only schema present is generic Yoast boilerplate (WebPage, Organization, SearchAction).

Impact: Google cannot generate hotel rich results (knowledge panel, star ratings, price ranges, direct booking links) for Vivere. AI engines like ChatGPT, Perplexity, and Claude have no structured facts to extract — so they pull from OTAs that DO have schema. This is the single biggest reason OTAs dominate Vivere’s branded and non-branded SERPs.

Competitive context: Acacia Hotel has AggregateRating schema showing 8.7/10 from 2,059 reviews. The Bellevue has LocalBusiness schema with full address, geo, and amenities. Vivere has none of this. In AI answer engines, the hotel with the richest structured data gets cited first.

Fix (estimated 4–6 hours, developer + SEO specialist):

Add Hotel schema (extending LodgingBusiness) to the homepage with: name, description, starRating (5), address, geo, telephone, url, image, amenityFeature, checkinTime, checkoutTime, numberOfRooms, priceRange, sameAs (all social profiles + TripAdvisor + Google Business)
Add FAQPage schema to /faq/ with all 92 Q&A pairs
Add Restaurant schema for The Nest and Shogun on /dine/
Add EventVenue schema to /celebrate/ and /meet/ with capacity data
Add AggregateRating from Google Business or TripAdvisor
Validate all schema via Google Rich Results Test and Schema.org validator

Critical #2: 92 FAQs with Zero FAQPage Schema

The /faq/ page contains 92 well-organized questions across 10 categories (General Info, Check-in/out, Rooms, Rates, Dining, Facilities, Events, Location, Policies, Booking). This is a massive content asset — but none of it is marked up with FAQPage structured data.

Impact: Google FAQ rich results show expandable Q&A directly in search results, increasing click-through rates by 20–40%. AI engines use FAQ schema as a primary extraction source for direct answers. With 92 questions, Vivere could own dozens of long-tail queries like “does Vivere Hotel have a pool,” “Vivere Hotel check-in time,” “Vivere Hotel parking.” Currently, all of this SEO value is being left on the table.

Fix (estimated 2–3 hours, developer):

Generate FAQPage JSON-LD with all 92 Q&A pairs
Inject into the /faq/ page <head> or before </body>
Validate with Google Rich Results Test
Submit /faq/ for re-indexing in Google Search Console

Critical #3: Multiple H1 Tags on 54% of Primary Pages

7 of 13 audited primary pages have more than one H1 tag. The homepage has 3 H1s (“Vivere Hotel Alabang,” “At the Heart of Everything,” “A Heaven of Artistic Expression”). Stay, Dine, Meet, Gallery, and Celebrate pages each have 2 H1s. Additionally, H1s are generic single words (“Stay,” “Dine,” “Meet”) with no target keywords.

Impact: Multiple H1s dilute the primary heading signal that search engines use to understand page topic. Generic H1s mean Google has no keyword-rich heading to associate with the page. The homepage’s actual visible hero text “At the Heart of Everything” is styled as H3 in some rendering contexts — the hierarchy is inconsistent.

Fix (estimated 3–4 hours, developer):

Homepage: Single H1 = “Vivere Hotel Alabang — Luxury Hotel in Filinvest City”
/stay/: Single H1 = “Rooms & Suites at Vivere Hotel Alabang”
/dine/: Single H1 = “Restaurants & Dining at Vivere Hotel”
/meet/: Single H1 = “Meeting & Conference Venues in Alabang”
/celebrate/: Single H1 = “Event Venues & Weddings at Vivere Hotel”
/gallery/: Single H1 = “Vivere Hotel Photo Gallery”
Demote all secondary H1s to H2

🔎 Detailed Findings

Click any row to expand. Ranked by severity.

#1 Critical Zero Hotel / LodgingBusiness schema on any page Schema ▶

Scope: Entire site (all 187 URLs)
Evidence: JSON-LD on homepage contains only WebPage, Organization, BreadcrumbList, WebSite, and SearchAction. No Hotel, LodgingBusiness, or LocalBusiness entity. Zero schema on all inner pages beyond Yoast defaults.
SEO/AEO Impact: No hotel knowledge panel. No rich results with star rating, price range, or amenities. AI engines cannot extract structured hotel facts — they default to OTA data instead. This is the #1 reason Vivere loses to competitors with schema.
Priority: Immediate — blocks all rich result eligibility.
Effort: 4–6 hours (developer + SEO specialist)

#2 Critical 92 FAQs on /faq/ with zero FAQPage schema Schema ▶

Scope: /faq/ (1 page, 92 questions, 10 categories)
Evidence: Page contains well-organized Q&A content across General Info, Check-in, Rooms, Rates, Dining, Facilities, Events, Location, Policies, Booking — but no FAQPage JSON-LD.
SEO/AEO Impact: Missing FAQ rich results for dozens of long-tail queries. AI engines cannot extract Q&A pairs for direct answers. Estimated 20–40% CTR increase once implemented.
Priority: Immediate — highest ROI fix on the site.
Effort: 2–3 hours (developer)

#3 Critical Multiple H1 tags on 7 of 13 primary pages (54%) On-Page ▶

Scope: Homepage (3 H1s), /stay/ (2), /dine/ (2), /meet/ (2), /celebrate/ (2), /gallery/ (2), /press-release/ (2)
Evidence: Elementor sections each have their own H1 element. Visible hero text coded inconsistently (sometimes H1, sometimes H3 depending on section).
SEO/AEO Impact: Diluted heading signals. Google cannot identify the primary topic of each page. Keyword targeting is impossible when H1s are “Stay,” “Dine,” “Meet” without context.
Priority: High — foundational on-page fix.
Effort: 3–4 hours (developer in Elementor)

#4 Critical ~80% of site images missing alt text Image SEO ▶

Scope: Gallery (20/20 missing), Stay (13/13 missing), Dine (8/8 missing), Specials (9/9 missing), Press Release (6/6 missing). Only homepage has partial coverage (~11/18).
Evidence: Image tags in HTML have empty or absent alt attributes across all audited inner pages.
SEO/AEO Impact: Google Image Search cannot index hotel photos. Screen readers cannot describe content (accessibility violation). Missing alt text means zero keyword signal from visual content. For a hotel, images ARE the product — this is especially damaging.
Priority: High — affects accessibility compliance and image search traffic.
Effort: 4–6 hours (content team + developer for bulk update)

#5 High OTAs dominate 5 of 8 high-intent queries — zero Vivere presence AEO ▶

Scope: “best hotel in Alabang,” “luxury hotel near Festival Mall,” “business travel Alabang,” “best hotels Muntinlupa,” “5 star hotel south of Manila”
Evidence: Booking.com, Expedia, Agoda, Hotels.com, TripAdvisor own all 10+ result positions. Vivere’s own domain does not appear. Competitors like Acacia (8.7/10, 2,059 reviews) and Bellevue are named directly by AI engines.
SEO/AEO Impact: Lost direct bookings. OTA commission cost on bookings that should come through viverehotel.com.ph. Brand authority eroded when OTAs present Vivere as one of many options rather than the anchor property.
Priority: High — requires content + schema strategy (see 30-Day Plan).
Effort: Ongoing — content creation + schema deployment over 4–8 weeks

#6 High Duplicate content: /stay/ and /rooms/ serve the same purpose Technical ▶

Scope: 2 URL paths (/stay/ in main nav + /rooms/ in sitemap) both list the same 6 room types.
Evidence: /stay/ is the active navigation page. /rooms/ exists in the rooms-sitemap.xml (7 entries, lastmod 2022) and is linked from legacy content. Both pages lead to the same room detail pages at /rooms/{room-type}/.
SEO/AEO Impact: Crawl budget waste. Potential duplicate content penalty. Link equity split between two URLs for the same topic. Similarly, /stories/ and /blog/ are separate content hubs with 12 and 107 posts respectively.

Fix:

301 redirect /rooms/ → /stay/ (keep /stay/ as canonical)
301 redirect /blog/ → /stories/ (or consolidate the 107 posts worth keeping)
Update internal links and sitemap accordingly
Remove /rooms/ and /blog/ from sitemap

#7 High Robots.txt sitemap URL uses www. but site runs on bare domain Technical ▶

Scope: robots.txt (site-wide)
Evidence: robots.txt: Sitemap: https://www.viverehotel.com.ph/sitemap.xml but canonical domain is viverehotel.com.ph (no www).
SEO/AEO Impact: Search engine crawlers may follow the www URL, hit a redirect, and potentially not discover all sitemap entries on first crawl. While Cloudflare likely redirects www → non-www, the unnecessary redirect adds latency to sitemap discovery.

Fix:

Update robots.txt to: Sitemap: https://viverehotel.com.ph/sitemap.xml
Verify in Google Search Console that the correct sitemap is submitted

#8 High Negative TripAdvisor review dominates branded SERP E-E-A-T ▶

Scope: Branded search query “Vivere Hotel Alabang reviews”
Evidence: TripAdvisor result titled “The worst hotel in Alabang” appears on page 1 of branded results. viverehotel.com.ph ranks #2 (homepage), but OTA review pages dominate positions 1 and 3–10.
SEO/AEO Impact: Negative review titles in branded SERPs erode trust before a visitor even clicks. Prospects searching the brand see the negative title before reaching viverehotel.com.ph. No structured AggregateRating schema to counter with a composite positive score.

Fix:

Implement AggregateRating schema on homepage with overall review score
Actively respond to the negative TripAdvisor review
Launch a review acquisition campaign (50+ new reviews in 90 days)
Publish a /reviews/ or /guest-experiences/ page to own more branded SERP slots

#9 High Organization schema has empty description and limited sameAs Schema ▶

Scope: Homepage JSON-LD
Evidence: Organization entity has "description": "" (empty string). sameAs array contains only Facebook and Instagram — missing TripAdvisor, Google Business Profile, LinkedIn, YouTube (if any).
SEO/AEO Impact: Google’s knowledge graph cannot associate Vivere with a description or full social presence. AI engines use Organization schema to verify brand identity and trustworthiness. Empty description = missed brand signal.

Fix:

Fill Organization description: “Vivere Hotel is a 5-star luxury hotel in Filinvest City, Alabang, Muntinlupa, Philippines. Established in 2001, the 31-story landmark offers rooms, suites, restaurants, and event venues.”
Add TripAdvisor, Google Business, and any other profile URLs to sameAs

#10 Medium Homepage HTML is 251 KB with 30+ separate CSS files Technical ▶

Scope: Homepage
Evidence: Raw HTML document is 257,289 bytes. 30+ individual Elementor widget CSS files loaded in <head>. Large inline <style> blocks for WordPress global styles, dominant-color, view-transitions.
SEO/AEO Impact: Bloated HTML increases Time to First Byte and First Contentful Paint. Each CSS file is a separate HTTP request (mitigated somewhat by HTTP/2 multiplexing). Google considers page speed in ranking signals, especially on mobile.

Fix:

Enable Elementor’s “Improved Asset Loading” to conditionally load CSS
Audit WP Rocket settings: enable CSS file optimization (combine/minify)
Remove unused Elementor widget CSS files
Enable Cloudflare page caching (move from DYNAMIC to HIT)

#11 Medium Thin content on Dine (450 words), Gallery (250 words), Contact (450 words) Content ▶

Scope: /dine/, /gallery/, /contact/
Evidence: /dine/ has ~450 words with no specific restaurant names in headings (The Nest and Shogun are buried in body). /gallery/ has ~250 words and is mostly images with zero alt text. /contact/ has ~450 words.
SEO/AEO Impact: Thin pages may not rank for target keywords. /dine/ should be a pillar page for “restaurants in Alabang” and “rooftop dining Manila” queries. Gallery should support image search traffic with descriptive content.

Fix:

/dine/: Expand to 800+ words with dedicated sections for each restaurant (The Nest, Shogun), menus, hours, reservation info
/gallery/: Add descriptive paragraphs per gallery section + alt text on all 20+ images
/contact/: Add travel directions, nearby landmarks, transportation tips (content already exists on homepage — consolidate)

#12 Medium 107 legacy blog posts (2018–2020) are stale, thin, or COVID-era content Content ▶

Scope: post-sitemap.xml (107 URLs)
Evidence: Bulk posts from 2018–2020 include COVID safety protocols, generic hotel tips, and thin promotional content. Only 2 recent posts (2026) in this sitemap. The active content hub (/stories/) has 12 entries, 7 of which are 2026-era quality content.
SEO/AEO Impact: Stale content can drag down domain quality signals. Outdated COVID content may confuse visitors and AI engines. Two separate blog hubs (/blog/ + /stories/) fragment authority.

Fix:

Audit 107 posts: keep evergreen content, 301 redirect or noindex dated/thin posts
Update high-traffic posts with current information
Consolidate into a single content hub (/stories/)
301 redirect /blog/ to /stories/

#13 Medium Malformed URL in story-sitemap.xml Technical ▶

Scope: 1 URL in story-sitemap.xml
Evidence: viverehotel.com.ph/stories/https-viverehotel-com-ph-hotels-near-naia-terminal-best-stays-manila-airport/ — the slug literally contains a URL instead of being a proper slug.
SEO/AEO Impact: Crawl error in Search Console. Wasted crawl budget. Unprofessional URL structure if indexed.

Fix:

Rename the story slug to /stories/hotels-near-naia-terminal-manila-airport/
301 redirect old URL to new

#14 Medium og:image is a small Elementor thumbnail, not a proper social card On-Page ▶

Scope: Homepage
Evidence: og:image points to /wp-content/uploads/elementor/thumbs/2-1-qo30esd...dc.png — an auto-generated Elementor thumbnail, not a designed 1200×630 social sharing image.
SEO/AEO Impact: When the homepage is shared on Facebook, LinkedIn, Twitter, or WhatsApp, the preview image is a small, low-quality thumbnail instead of a professional hotel hero image. First impressions matter for social referral traffic.

Fix:

Create a 1200×630px branded social card image (hotel hero shot + logo)
Set as og:image and twitter:image in Yoast’s Social tab
Repeat for all major pages (Stay, Dine, Meet, Celebrate)

#15 Medium H2 hierarchy contains non-semantic entries On-Page ▶

Scope: Homepage (21 H2s)
Evidence: “25 years,” “#viveremoments,” and “Follow Us” (duplicated) are H2 tags. Promo names like “Mex-Med Chef’s Corner Special” and “Vivere Halo Halo” are H2s. Footer sections (Address, Phone, Emails) are H2s.
SEO/AEO Impact: 21 H2s on a single page dilutes heading structure. Non-semantic entries confuse topic modeling. Footer content should not use heading tags.

Fix:

Reduce homepage to 6–8 meaningful H2s (Rooms & Suites, Dining, Events, Location, etc.)
Demote promo names to H3 or styled text
Remove heading tags from footer elements (use styled <div> or <span>)

#16 Medium No Restaurant schema for The Nest or Shogun Schema ▶

Scope: /dine/ page
Evidence: The Nest (rooftop dining, the hotel’s signature venue) and Shogun (Japanese restaurant) are mentioned on the homepage and /dine/ but have no Restaurant schema with cuisine type, menu, hours, or servesCuisine.
SEO/AEO Impact: “Rooftop restaurant Alabang” and “Japanese restaurant Alabang” queries cannot trigger rich results. The Nest blog post ranks well organically, but Restaurant schema would add a second ranking pathway via Google’s restaurant knowledge panel.
Effort: 2 hours (developer)

#17 High All 6 inner-page title tags are critically short (18–24 chars vs 50–60 recommended) On-Page ▶

Scope: All primary inner pages (verified from raw HTML)
Evidence (verified May 8, 2026):

Page	Title Tag	Chars
/stay/	Stay \| Vivere Hotel	19
/dine/	Dine \| Vivere Hotel	19
/meet/	Meet \| Vivere Hotel	19
/celebrate/	Celebrate \| Vivere Hotel	24
/specials/	Specials \| Vivere Hotel	23
/faq/	FAQ \| Vivere Hotel	18

SEO/AEO Impact: Google truncates titles at ~60 chars but rewards keyword-rich titles. These single-word titles waste 30–40 chars of SERP real estate. No location keywords (Alabang, Manila), no service keywords (Rooms, Restaurants, Events). Competitors’ title tags include location and service modifiers that help them rank.

Recommended titles:

/stay/ → “Rooms & Suites at Vivere Hotel Alabang | Book Direct” (52 chars)
/dine/ → “Restaurants & Rooftop Dining at Vivere Hotel Alabang” (52 chars)
/meet/ → “Meeting & Conference Venues in Alabang | Vivere Hotel” (53 chars)
/celebrate/ → “Event Venues & Weddings at Vivere Hotel Alabang” (48 chars)
/specials/ → “Hotel Deals & Packages | Vivere Hotel Alabang” (46 chars)
/faq/ → “Frequently Asked Questions | Vivere Hotel Alabang” (50 chars)

#18 High Meta descriptions: 1 too short (23 chars), 2 too long, 1 generic placeholder On-Page ▶

Scope: All primary inner pages (verified from raw HTML)
Evidence (verified May 8, 2026):

Page	Meta Description	Chars	Status
/stay/	Stay with us at our cleanest and most relaxing rooms. Plan your next staycation…	124	OK but weak
/dine/	Dining in one of the best restaurants in the South should definitely be…	195	Too long
/meet/	Have a meeting or event planned out but you don’t have a venue…	141	OK but weak
/celebrate/	Celebrate your milestones with Vivere hotel today…	144	OK
/specials/	Unlock exclusive savings now! Discover current promotions… products and services.	167	Too long + generic
/faq/	Book your stay with us.	23	Placeholder

SEO/AEO Impact: /faq/ has a 23-char placeholder — Google is auto-generating snippets for the site’s most content-rich page. /specials/ uses generic “products and services” language that doesn’t mention the hotel. /dine/ at 195 chars will be truncated. None contain location keywords.

Fix:

/faq/ → “Find answers to 92 frequently asked questions about Vivere Hotel Alabang — rooms, check-in, dining, events, parking, and more.” (131 chars)
/specials/ → “Explore current hotel deals, dining promos, and staycation packages at Vivere Hotel Alabang. Book direct for exclusive rates.” (126 chars)
/dine/ → Trim to 155 chars with restaurant names (The Nest, Shogun) and “Alabang”
All descriptions should include “Vivere Hotel,” “Alabang,” and a CTA

#19 Low Broken link: /specials/vivere-halo-halo/ 301 redirects to /specials/ (promo expired) Technical ▶

Scope: 1 URL (verified link check: 40 URLs tested, May 8, 2026)
Evidence: /specials/vivere-halo-halo/ returns HTTP 301 redirecting to /specials/. The promo has been unpublished. However, the homepage still links to it in the “Just For You” specials section. All other 39 URLs tested return HTTP 200. Zero 404s or 5xx errors found.
SEO/AEO Impact: Low impact — the 301 redirect is properly handled. However, users clicking the homepage link expect the specific promo and land on the generic Specials page instead. A minor UX issue.
Additional verified positives: HTTP→HTTPS redirect works. www→non-www redirect works. Trailing-slash canonicalization is consistent. /rooms/ and /stay/ both return 200 (duplicate, but no redirect loop). All 10 venue pages, 6 room pages, and 4 active specials pages return 200.

Fix:

Remove the Vivere Halo Halo link from the homepage specials section
Replace with an active promo or remove the card entirely

#20 Medium All inner pages use og:type “article” instead of “website” On-Page ▶

Scope: 5 of 6 verified inner pages (verified from raw HTML)
Evidence: /stay/, /dine/, /meet/, /celebrate/, and /faq/ all have og:type = article. Only /specials/ correctly uses og:type = website. These are landing pages, not articles.
SEO/AEO Impact: Low direct impact on ranking, but og:type informs social platforms how to present shared links. “article” type may show publication dates or author info that don’t apply to landing pages. Correct og:type improves social sharing presentation.

Fix: In Yoast SEO settings, set og:type to “website” for all non-article pages (landing pages, category pages).

#21 Win Zero broken links across 40 tested URLs (verified) Technical ▶

Scope: 40 internal URLs tested (May 8, 2026)
Evidence: All 15 navigation pages, 6 room pages, 10 venue pages, 4 active specials, /blog/, /alabang-wedding-venue/, /compare-rooms/, and redirect targets all return HTTP 200. Only 1 soft redirect found (/specials/vivere-halo-halo/ → /specials/). HTTP→HTTPS, www→non-www, and trailing-slash redirects all function correctly.
Impact: Clean link structure means no crawl budget waste from 404s. Users and bots can navigate the full site without dead ends. This is a solid technical foundation.

#22 Win llms.txt exists — ahead of virtually all competitors AEO ▶

Scope: /llms.txt (auto-generated by Yoast SEO v27.5)
Evidence: Structured file with Pages (5), Posts (2), Media Features (5), Venues (5), Careers (5), Stories (7), Rooms (4), Specials (7), Categories (2). Includes descriptions for stories and specials. Links to sitemap index.
AEO Impact: Positive signal for AI crawlers (ChatGPT, Claude, Perplexity). Most Philippine hotels do not have llms.txt. This gives Vivere an early-mover advantage in AI indexing.
Enhancement: Currently only surfaces a subset of pages (e.g., 2 of 107 blog posts). Expand to include all active room pages, venue pages, and the FAQ page for maximum AI coverage.

#23 Win The Nest rooftop content ranks in AI search — textbook AEO AEO ▶

Scope: /stories/the-nest-rooftop-dining-alabang-manila/
Evidence: This blog post is cited by AI engines for “hotel with rooftop bar Alabang Manila” queries. Facts extracted: name, address, hours (open daily from 4PM), cuisine, features (rooftop pool, terrace, Laguna de Bay views). The only competitor cited alongside is The Bellevue’s Vue Bar.
AEO Impact: This single content piece proves the AEO content model works. Fact-rich, intent-matching, answerable content gets cited. The strategy should be replicated for every high-intent query where Vivere is currently invisible.

#24 Win Event/wedding pages rank well with extractable data AEO ▶

Scope: /venues/ and /alabang-wedding-venue/
Evidence: For “hotel with event venue Alabang Manila,” two Vivere pages appear in top results. AI engines extract: 12 unique venues, capacity up to 300 guests for weddings. Competitors cited (Acacia, Bellevue, B Hotel) have less specific capacity data.
AEO Impact: Events and weddings are a significant revenue stream. These pages prove that specific, data-rich content earns AI citations. Adding EventVenue schema would further strengthen this position.

#25 Win Strong infrastructure: Cloudflare, HTTPS, HTTP/2+3, WP Rocket Technical ▶

Scope: Site-wide infrastructure
Evidence: Cloudflare CDN (Hong Kong POP), HSTS enforced (max-age=31536000), HTTP/2 + HTTP/3 (alt-svc h3), comprehensive security headers (CSP, X-Frame-Options, XSS Protection, Permissions-Policy, Referrer-Policy). WP Rocket defers JS via rocketlazyloadscript pattern. Fonts served locally as WOFF2. Hero image preloaded as WebP with fetchpriority=high.
AEO Impact: No bot-blocking WAF issues detected (unlike the Sky High reference audit). Googlebot, Bingbot, ChatGPT-User, ClaudeBot, PerplexityBot, and Applebot should all have clean crawl access. This is a solid foundation to build on.

🤖 AI Answer Engine Optimization (AEO) Audit

Methodology: 8 representative customer-intent queries were tested across web search and AI answer engines to assess how likely viverehotel.com.ph is to be cited. Queries cover branded, non-branded, feature-specific, geographic, and competitive intents relevant to a 5-star hotel in Alabang, Muntinlupa.

Test Query	Vivere Cited?	Position / Detail	Top Competitor Cited
“best hotel in Alabang Muntinlupa”	Mentioned only	No direct link; mentioned as distance data point in OTA aggregations	B Hotel (8.8), Acacia (8.7), Azumi (8.8)
“luxury hotel near Festival Mall Alabang”	NO	Completely absent from results	B Hotel, Bellevue (8.6), Azumi, Acacia
“hotel with rooftop bar Alabang Manila”	YES	Own-domain blog post ranks. Rich detail extracted: name, address, hours, cuisine, views	Bellevue (Vue Bar, 22nd floor)
“where to stay in Alabang for business travel”	NO	Absent from all results	Bellevue, Hop Inn, Heritage Hotel
“best hotels in Muntinlupa City Philippines”	Mentioned only	Named in OTA summaries with generic description; no direct link. Price: PHP 4,017	Acacia (“most popular 5-star,” 8.7, 2,059 reviews)
“Vivere Hotel Alabang reviews”	YES	#2 position (homepage). BUT negative TripAdvisor title appears on page 1	OTAs dominate (Hotels.com, Booking, TripAdvisor, Agoda)
“hotel with event venue Alabang Manila”	YES	Two pages rank (/venues/, /alabang-wedding-venue/). 12 venues, 300-guest capacity extracted	Acacia (Grand Ballroom), Bellevue (20/20 Room)
“5 star hotel south of Manila Philippines”	NO	Completely absent. SERP dominated by Makati/Pasay properties	Peninsula Manila, Diamond Hotel, Nuwa/City of Dreams

3 / 8

Queries Where Vivere Is Cited

2 / 8

Partial Mention (OTA Only)

3 / 8

Completely Absent

Key AEO insight: The content model that works (fact-rich, intent-matching, query-answering articles like the Nest rooftop post) needs to be replicated for every high-intent query where Vivere is absent. Specifically: “business hotel Alabang,” “luxury hotel near Festival Mall,” and “5-star hotel south of Manila.” Additionally, Hotel schema with AggregateRating would give AI engines structured facts to cite instead of falling back to OTA summaries.

⚖️ Competitive Landscape

Brand	Trust Framing	Rating / Reviews	Schema Depth	Content Depth	AI Answer Rank
Vivere Hotel	25 years, DOT accredited, Travel + Leisure awards	No score in schema; TripAdvisor mixed	Minimal (WebPage + Org only)	92 FAQs, 12 stories, 11 venues	Cited in 3/8 queries
Acacia Hotel Manila	Major chain, 5-star positioning	8.7/10, 2,059 reviews	Structured review data	Strong: business center, event spaces, dining	Named in 4/8 queries
The Bellevue Manila	Premium property, 6 dining options, spa	8.6/10	LocalBusiness with full address + geo	Strong: Vue Bar content, business center, 525 sqm event space	Named in 5/8 queries
Azumi Boutique Hotel	Eco-chic positioning, boutique appeal	8.8/10	Basic	Niche: rooftop infinity pool, eco-friendly messaging	Named in 3/8 queries
B Hotel Alabang	Modern luxury, newer property	8.8/10	Basic + event venue data	Moderate: function rooms, music lounge	Named in 3/8 queries
Somerset Alabang Manila	Ascott brand, long-stay serviced apartments	Not prominently featured	Brand-level schema	Extended-stay niche: kitchenettes, corporate housing	Named in 2/8 queries
Hop Inn Alabang	Budget-friendly, Madrigal Business Park	Not prominently featured	Basic	Minimal: budget positioning, proximity content	Named in 2/8 queries

Competitive diagnosis: The Bellevue is Vivere’s most dangerous competitor — it appears in 5 of 8 queries and owns the “business hotel” and “luxury hotel” positioning. Acacia competes on structured review data (8.7/10 with 2,059 reviews) that AI engines love to cite. Azumi and B Hotel punch above their weight with higher OTA ratings (8.8/10) despite being smaller properties. Vivere’s competitive advantage (25 years, largest event capacity, signature rooftop) is not being communicated in machine-readable format. The brand has the strongest real-world story in the set but the weakest digital expression of it.

🚀 30-Day Action Plan

Week 1 — Foundation: Schema & Technical Fixes

Action ItemOwnerEffortImpact

Add Hotel/LodgingBusiness schema to homepage (star rating, address, geo, amenities, check-in/out, priceRange, sameAs) Developer 4–6h Critical

Add FAQPage schema to /faq/ with all 92 Q&A pairs Developer 2–3h Critical

Fix all multiple-H1 pages: single keyword-rich H1 per page, demote extras to H2 Developer 3–4h High

Fix robots.txt sitemap URL (remove www. prefix) Developer 15min Medium

Fix malformed URL in story-sitemap.xml Developer 30min Medium

Fill Organization schema description and expand sameAs array Developer 30min Medium

301 redirect /rooms/ → /stay/ and /blog/ → /stories/ Developer 1h Medium

Week 2 — On-Page, Image SEO & AEO Reinforcement

Action ItemOwnerEffortImpact

Add alt text to ALL images site-wide (~100+ images). Use descriptive, keyword-relevant alt text Content + Dev 4–6h High

Add Restaurant schema for The Nest and Shogun on /dine/ Developer 2h Medium

Add EventVenue schema to /celebrate/ and /meet/ with capacity data Developer 2h Medium

Create 1200×630 OG images for homepage + 5 primary pages Designer 3h Medium

Clean up H2 hierarchy on homepage: reduce from 21 to 6–8 semantic headings Developer 2h Medium

Expand llms.txt to include all room pages, venue pages, and /faq/ Developer 1h Medium

Enable Cloudflare page caching (move from DYNAMIC to cached) Developer 1h Medium

Week 3 — Content, Local SEO & Trust Signals

Action ItemOwnerEffortImpact

Publish AEO content: “Best Business Hotels in Alabang — Corporate Traveler’s Guide” Copywriter 1 day High

Publish AEO content: “Luxury Hotels in Alabang Near Festival Mall” Copywriter 1 day High

Expand /dine/ page to 800+ words with dedicated restaurant sections Copywriter 4h Medium

Add AggregateRating schema from Google Business or TripAdvisor Developer 2h High

Respond to negative TripAdvisor review; begin review acquisition campaign Marketing Ongoing High

Audit 107 legacy blog posts: noindex thin/dated posts, 301 redirect duplicates SEO + Dev 1 day Medium

Optimize Google Business Profile: updated photos, hours, attributes, Q&A Marketing 3h Medium

Week 4 — Authority Building, Internal Linking & Measurement

Action ItemOwnerEffortImpact

Publish AEO content: “Why Alabang Is South Manila’s Best-Kept Hotel Destination” Copywriter 1 day High

Build internal linking hub: link new stories to /stay/, /dine/, /celebrate/, and vice versa SEO 3h Medium

Set up Google Search Console monitoring: index coverage, rich results, Core Web Vitals Developer 2h Medium

Submit updated sitemap and request re-indexing of schema-enriched pages Developer 1h Medium

Run follow-up AEO citation tests on all 8 queries to measure improvement SEO 2h Medium

Create a /reviews/ or /guest-experiences/ page to own more branded SERP slots Copywriter + Dev 4h Medium

🔭 Beyond 30 Days — 3 to 12 Month Strategy

Authority Content Program

Publish 2 AEO-style articles per month targeting high-intent queries: “wedding venues in Alabang,” “corporate event space south of Manila,” “staycation packages Muntinlupa,” “rooftop restaurants Metro Manila.” Each article should be 1,500+ words, fact-rich, with FAQ sections and internal links to booking pages.

Review Acquisition Campaign

Target 100+ new Google and TripAdvisor reviews within 6 months. Implement post-checkout email/SMS review requests. Respond to all reviews within 48 hours. Goal: raise visible aggregate score to 8.5+ to compete with Acacia (8.7) and Azumi (8.8).

Local SEO Expansion

Optimize Google Business Profile monthly (new photos, updated attributes, Q&A). Build local citations on Philippine directories (Tripadvisor.com.ph, Philippine Star, Inquirer). Create “nearby attractions” content hub linking to Alabang Town Center, Festival Mall, Filinvest landmarks.

Digital PR & Backlinks

Leverage Travel + Leisure awards and 25th anniversary narrative for press coverage. Target Philippine travel bloggers, lifestyle publications, and wedding planning sites. Each earned backlink strengthens domain authority for competitive hotel queries.

Schema Expansion

Add schema to every room page (HotelRoom with bed type, amenities, occupancy). Add Offer schema to /specials/ with validity dates. Add BreadcrumbList to all pages. Add VideoObject if virtual tours exist. Goal: become the most schema-rich hotel site in Alabang.

Conversion Optimization

A/B test booking CTAs on room pages. Add urgency signals (availability, recent bookings). Implement exit-intent offers. Track direct booking conversion rate vs. OTA referrals. Goal: shift 10% of OTA bookings to direct.

AI-Citable Content Library

Build a structured knowledge base: “Everything you need to know about [topic] at Vivere Hotel.” Topics: weddings, corporate events, dining, suites, Alabang guide. Each page = a potential AI citation source. Bold key answer sentences for extraction.

Analytics & Tracking

Set up Search Console rich results monitoring. Track AI citation frequency monthly (re-run the 8-query test). Monitor branded SERP reputation. Track organic traffic by landing page. Set up goal tracking for direct bookings vs. OTA clicks.

📚 Methodology

Sitemaps Parsed

Main sitemap index + 9 child sitemaps (pages, posts, rooms, venues, specials, careers, stories, press releases, categories). 187 total URLs catalogued.

Pages Deep-Audited

Representative sample including all 13 primary navigation pages, 6 room pages, 10 venue pages, sample specials and stories. 6 inner pages verified from raw HTML for exact title tags, meta descriptions, OG tags, and canonical URLs.

URLs Link-Checked

All navigation pages, room pages, venue pages, active specials, and key content pages tested for HTTP status codes. 39 returned 200, 1 returned 301 (expired promo). Zero 404s or 5xx errors.

AEO Citation Tests

Live web search queries across branded, non-branded, feature-specific, geographic, and competitive intents. Results analyzed for citation presence, position, and fact extraction.

Competitors Benchmarked

Acacia Hotel, The Bellevue, Azumi Boutique, B Hotel, Somerset Alabang, Hop Inn. Compared on trust signals, schema depth, content, ratings, and AI citation frequency.

Tools & checks used: Direct HTML source analysis, sitemap parsing, robots.txt inspection, JSON-LD schema extraction, HTTP header analysis, heading hierarchy audit, image alt-text audit, content word-count estimation, web search result analysis for AEO citation testing.

Verification passes completed: (1) Raw HTML extraction of title tags, meta descriptions, OG tags, and canonical URLs on 6 key inner pages — all values verified and reported with exact character counts. (2) Broken link check across 40 internal URLs — all HTTP status codes confirmed. (3) Schema markup verified by parsing JSON-LD from page source.

Lighthouse scores verified: PageSpeed Insights run manually on May 8, 2026 — Mobile (Performance 63, Accessibility 100, Best Practices 96, SEO 100) and Desktop (Performance 95, Accessibility 90, Best Practices 100, SEO 100). Core Web Vitals individual metrics (FCP, LCP, TBT, CLS) were not captured from the report. Google Search Console data was not available. OTA review scores are approximate based on search result snippets. Image alt-text counts are estimates from 6 sampled pages, not a full crawl of all 187 URLs.

Assumptions: The site is accessible to all major search engine and AI crawlers (no WAF blocking detected, unlike the reference audit). Cloudflare is on a free or Pro plan based on cache behavior. WordPress is the confirmed CMS (Elementor 4.0.6 + Yoast SEO 27.5).