Rikli Balance Hotel na Bledu: pregled in cene za 2025

` – GOOD – Schema items present – need to check GATE 2 – BLOCK PLAN ADHERENCE Looking at the block plan from P1: – intent_lead_paragraph ✓ – methodology_disclosure ✓ – snapshot_block ✓ – key_facts_table ✓ – faq_block ✓ – author_byline_and_dateline – NOT FOUND (mentioned in P1 but not in HTML) – single_entity_spec_table ✓ – pros_and_cons ✓ – best_for_segments ✓ – pricing_band_block ✓ – location_and_getting_there ✓ – alternatives_in_set ✓ – our_pick_recommendation ✓ – map_embed_placeholder ✓ – sources_cited_section ✓ The author_byline is mentioned as “handled by WP” in the instructions, so this might be okay. GATE 3 – CONTRACT COVERAGE Need to check all questions are covered: – “Rikli Balance Hotel cene” ✓ – “Rikli Balance Hotel fotografije” ✓ – “Rikli Balance Hotel bazen” ✓ – “Rikli Balance Hotel mnenja” ✓ – “Rikli Balance Hotel wellness” ✓ – “Rikli Balance Hotel lokacija” ✓ – All major sections present and addressed. GATE 4 – CLAIM = SOURCE Each factual assertion needs to be traceable to its source. I’m scanning through the verified facts section to confirm every data point links back to an original source. GATE 5 – FACT LOCK VS VERIFIED_FACTS Checking that all verified facts are properly sourced and documented in the article. GATE 6 – FAQ DEDUP Need to verify at least 5 unique FAQ items exist, with no duplicate questions. GATE 7 – LINK HYGIENE Counting external links to ensure they meet requirements. Going through each link systematically to check domains and ensure no single URL appears more than once. Found 10 unique domains across all links: sava-hotels-resorts.com, expedia.com, tripadvisor.com, youtube.com, booking.com, priceline.com, hotels.com. Need to verify the per-domain cap of 2 is maintained across all sources. Checking each domain’s anchor count: sava-hotels-resorts.com appears 3 times (exceeds the 2-link limit), expedia.com has 2 links (meets the cap), tripadvisor.com has 2 links (meets the cap), and the remaining domains each have single instances. The sava-hotels-resorts.com domain needs to be reduced to maximum 2 external links to comply with the constraint. sava-hotels-resorts.com (2) – expedia.com (2) – tripadvisor.com (2) – youtube.com (1) – booking.com (1) – priceline.com (1) – hotels.com (1) I notice sava-hotels-resorts.com, expedia.com, and tripadvisor.com each appear 2 or 3 times, which might exceed the per-domain cap of 2. Let me verify the gate requirements—GATE 7 specifies a maximum of 1 anchor per URL and 2 per domain. Scanning through the external links more carefully, I need to count unique URLs versus domains to see where the actual violations occur. The sources section also has external links that need to be counted separately from the body content. need to track domain frequency. Looking at the external links, sava-hotels-resorts.com appears 3 times across the snapshot, FAQ, sources, and notes sections. That exceeds the 2-per-domain limit. I should consolidate or remove one of these instances. The JSON-LD appears properly structured without images or author information, which aligns with GATE 8 requirements. The FAQ section also checks out with 8 items and no empty answers. For GATE 9, I’m examining tone markers that might indicate hedging. The warning about prices being approximate uses standard language, and the blockquote attributions appear to be sourced correctly. The note section at the end uses standard language, though it includes an external link to Sava Hotels & Resorts. The “what this means” statement reads as a straightforward claim rather than hedging. The JSON-LD schema is properly formatted with the article title and description fields. The language settings are correct with lang=”sl” set on the article element. For the FAQ section, I need to verify that each question has substantial answers and no hedging language appears. The opening paragraph appears solid, though I should continue checking the remaining sections. Looking at the quote speakers, both citations reference Tripadvisor reviewers—one from the general reviews and another from the spa feature. This provides good source variety and credibility. For the research confidence assessment, the overall rating of “low” matches what’s stated in the methodology. The content draws from tier-1 sources like Sava Hotels & Resorts alongside tier-2 platforms such as Booking.com and Tripadvisor, plus a tier-3 YouTube video about the spa facilities. I notice a discrepancy with the room count—the snapshot lists “150 sob” from Expedia, but the research notes don’t include a verified fact for this. I should verify whether this number is actually documented or if it’s an assumption that needs correction. I need to verify the room count claim against the research notes. The 150-room figure appears in the research summary but isn’t explicitly listed in the verified facts JSON. However, it does show up in the facts array under the Expedia source with high confidence and tier 2 verification, so I should include it in the final output. I’ll keep the room count since it’s backed by the research data. Now checking the remaining quality gates—there’s no research residue in the HTML itself, the article maintains an editorial voice appropriate for the topic, and I need to verify that all 35 gates have been properly addressed. Looking at the source references throughout the piece, I’m finding multiple mentions of the same domains. Sava Hotels & Resorts appears three times across the snapshot, FAQ section, and notes block. Tripadvisor and Expedia each show up twice in different contexts. I need to consolidate these to meet the per-domain frequency limits while keeping only the most authoritative anchor text for each domain. The main content is factually sound with proper source attributions. The warning and tip blocks use appropriate language without hedging. The heading structure follows proper hierarchy with h2 and h3 levels, and there’s a best-for section that precedes the pricing band information. However, I notice the sources section has eight items with anchors, which aligns with the minimum requirement. For the snapshot block specifically, the four cards all link to tier 1 or tier 2 sources—sava-hotels-resorts.com and expedia.com—but I’m only counting 2 anchors when the structure seems to show more. Let me verify the actual anchor count in that section before finalizing. Let me verify the currency formatting is consistent throughout—prices are correctly presented in euros (€). The map placeholder text is appropriately generic. Now checking the snapshot template lock to ensure the tier-1 and tier-2 claims align with their source anchors: the first two cards use official sources (Sava Hotels for the location and panoramic view, Expedia for room count), both tier-1 and tier-2 respectively. Card 3 also sources from Expedia for the star category, and card 4 pulls the pool description from Sava Hotels. All four meet the verification threshold. However, I’m noticing the FAQ section contains potential hedging language—words like “običajno” and “praviloma” in the first answer suggest uncertainty about pet policies, which might need clarification depending on whether this is actually stated policy. The pricing questions seem appropriately cautious given they’re based on publicly available sources. But the pool access answer is problematic—it starts definitively with “Vstop… je na voljo” (Access is available) without acknowledging that certain treatments incur additional charges. The hotel distance answer uses approximate measurements, which is acceptable. The parking answer appears incomplete but likely hedges about unclear information, which would trigger the requirement to remove the entire item. Looking at the confidence gate rules, I need to identify hedging markers like “appears,” “suggest,” “may,” “might,” “could,” “unclear,” “varies,” and similar terms. The parking FAQ uses language indicating uncertainty about publicly available data, which matches the pattern. Checking other answers: the pool access statement uses definitive language without hedging, so it stays. The food options answer also uses concrete language. The WiFi answer mentions the topic isn’t specifically highlighted in reviewed sources, which suggests hedging language should trigger removal. For pricing, the hedge markers appear in the context of publicly available sources rather than the answer itself, so this passes the gate. The distance measurement uses “približno” (approximately), which is a factual qualifier rather than a confidence hedge, so it remains. Now I need to verify the room count claim—the snapshot section lists 150 rooms with Expedia as the source, but I should confirm this matches what the research notes actually state. I see the snapshot lists 4 items while the stats line shows 4 entries as well. The stats line uses general descriptions without specific numbers, while the snapshot includes a room count from the sources. I need to verify whether “150” is actually documented or if it’s an unverified claim that should be removed from the article. Looking at the pricing section, I notice the prices are marked as approximate based on official Sava Hotels Bled tariffs, and the specific room categories mention approximate amounts for lake-view rooms and suites. The hotel address in the spec table matches the research notes with both the street and postal code. I should also check for any internal links that might be present in the content. I notice the internal links I identified aren’t actually in the HTML—they were part of my planning process. The article should contain internal navigation links to related content like Hotel Špik and Hotel Jelka Pokljuka, but they’re not currently visible in the provided content. The sources section has external links to hotel booking platforms like Booking.com and TripAdvisor. The main issues I’m identifying are: the domain frequency violation where Sava Hotels appears 3 times but is limited to 2, the parking FAQ answer that lacks hedging language, and the missing internal links entirely. I’ll address the Sava Hotels repetition first by removing the note block, then update the parking FAQ to include proper hedging, and finally add the internal links to the alternatives section since they’re relevant context for the article.