Michiu / marketing reference

Finding Michiu's reviews across platforms

Where the reviews live, what they're listed under, and how to get them out as data the system can ingest.

Important historical context: Michiu hasn't always been called "Michiu". Before late 2024 the same address operated under several names — "Michiu Lounge", "Michiu Restaurant", "Michiu BV" — and aggregator platforms often still list the place under the older name (or have orphan review pages from the old listing). Search every platform under all four names before concluding it's not there.


Owner-controlled (you have admin access)

These are platforms where Michiu has a verified owner account. You log in, export, drop in imports/, run pnpm import:csv.

PlatformWhere to log inHas CSV export?Notes
Googlehttps://business.google.comAPI only — use pnpm import:googlePending Business Profile API approval
TheForkhttps://manager.thefork.comyes (recent reviews dashboard → export)NL+EU bookings + reviews
Iens(Iens redirects to TheFork manager since the merger)via TheFork"iens" reviews still get tagged on the source
OpenTablehttps://restaurant.opentable.comyessmall NL volume
Quandoohttps://restaurant.quandoo.comyessmall NL volume
Thuisbezorgdhttps://restaurants.thuisbezorgd.nlexport reviews via dashboarddelivery reviews — different audience than dine-in
Sitedishhttps://admin.sitedish.shop (or your custom storefront admin)check admin dashboardtakeaway storefront on sitedish.shop
Socialdealshttps://verkoper.socialdeals.nlreviews tied to past dealsusually has reviews from each deal redemption

Aggregator-only (no owner account, manual or third-party)

These sites scrape or aggregate from elsewhere. Michiu may not have a verified owner profile, so reviews must be pulled manually.

PlatformListing URL patternNotes
TripAdvisorhttps://www.tripadvisor.com/Restaurant_Review-g188590-d5794434-Reviews-Michiu-Amsterdam_North_Holland_Province.htmlverified listing; ~113 reviews per Wanderlog crawl. Strict scrape ToS — copy-paste only
Yelphttps://www.yelp.com/biz/michiu-amsterdamverified listing; usually tiny EU volume
RestaurantGuruhttps://restaurantguru.com/Michiu-Amsterdamverified — aggregator that re-hosts Google/TripAdvisor reviews. Beware double-counting if you've already imported from Google or TripAdvisor
Dinestardinestar.nl/restaurant/...small NL directory
Spontaanspontaan.nl/.../michiulast-minute booking; light review volume
Whynotwhynot.com or whynot.nlconfirm exact platform
Foursquare / Swarmhttps://foursquare.com/v/michiu/5224add911d2bd75848790eeverified, listed since 2013. Tips (≈mini-reviews) require login to scrape; copy-paste only

Facebook — needs consolidation BEFORE importing

Web research surfaced four separate Michiu pages on Facebook, almost certainly orphan duplicates from pre-2024 brand changes:

URLListed nameNotes
https://www.facebook.com/michiu102/"Michiu Lounge | Amsterdam"likely the active page; keep this one
https://www.facebook.com/people/Restaurant-Lounge-Michiu/100043262305921/"Restaurant-Lounge Michiu"orphan duplicate — merge or delete
https://www.facebook.com/pages/category/Sushi-Restaurant/Restaurant-Lounge-Michiu-508308612612685/"Restaurant-Lounge Michiu"second orphan duplicate — merge or delete
https://m.facebook.com/profile.php?id=579630392108669"Michiu" sushi restaurantthird orphan profile — investigate, claim or report

Action before importing Facebook reviews:

  1. Log in to Meta Business Suite as the verified owner
  2. Determine which of the 4 pages has the most followers / reviews / authentic activity
  3. Use Facebook's "Merge duplicate pages" tool (Settings → Page Info) to consolidate
  4. Once merged, export the recommendations + reviews via Meta Business Suite (no native CSV — copy-paste each, or use Meta Graph API)
  5. Then import via pnpm import:csv with source=facebook

This is high-leverage operational work — orphan pages dilute review counts, fragment SEO, and make Facebook ad targeting less effective.


CSV format for non-Google imports

All imports use the unified schema in imports/example.csv:

source,external_id,review_url,author_name,author_email,rating,review_text,
language,review_date,reply_text,reply_date,internal_notes

The source column must match one of the slugs in src/lib/reviews/types.ts (REVIEW_SOURCES const). All 15 platforms above are valid as of migration 0003_extend_review_sources.sql.

If the platform's CSV doesn't have a review id, leave external_id blank — the importer derives a stable id from source + date + author_slug so re-runs dedupe.


Practical workflow

  1. Pick a platform from the owner-controlled table.
  2. Log in to the owner dashboard, export reviews to CSV.
  3. Open in Excel / Numbers / LibreOffice. Map the columns to the unified schema (rename headers, fill in source and review_date columns, YYYY-MM-DD format).
  4. Save as imports/<platform>-2026-05.csv (any name, just keep .csv and not example.csv).
  5. Run pnpm import:csv.
  6. Repeat for the next platform.

Files in imports/ (other than example.csv) are gitignored — they contain guest PII and don't belong in version control.


Edge cases

  • Same review on two platforms. RestaurantGuru re-hosts Google and TripAdvisor reviews. If you import from both Google and RestaurantGuru, you'll get duplicates with different external_ids. Either skip RestaurantGuru after Google is wired up, or use the internal_notes column to mark the duplicate for filtering later.
  • Old-name reviews. Reviews from 2020-2024 may show authors who reviewed "Michiu Lounge" — they're still your reviews. Import them at face value.
  • Owner replies imported. If the platform's export includes the merchant's existing reply (TheFork, Thuisbezorgd both do), use the reply_text and reply_date columns. The importer marks them status='posted', prompt_version='imported', model_used='human' — preserved as historical record, never regenerated by the LLM.

Source: michiu-marketing/docs/finding-reviews.md. To edit, change the file in the repo and redeploy.