Feštaj should sell the experience. Gacka16 should become the place people instantly understand, search for, and remember. Below that strategy: exactly where the building work stopped, and the words to paste to start it again.
of 12 ads steps finished
of 16 rebuild steps started
decisions waiting on you
ads running · nothing spends
Three streams, all paused on purpose. Nothing is live, nothing spends money, and nothing on the old site has been touched.
hub repo
gacka repo
festaj repo · Wix
No account, price, date or event will be made up to fill one of these in. Each one waits for your answer, and the work around it carries on without it.
Copy one block into a fresh window and the work continues from exactly where it stopped. Both refuse to spend money, publish, or touch the live site.
Paste into a fresh window. Everything it needs is already on GitHub.
Continue a stopped plan dispatch in the hub repo. Plan file: <dev root>/hub/docs/plans/finish-the-ads-control-plane-and-launch-safely.md Read it first, including the "Run status" block near the top, plus docs/reports/ads-launch-what-actually-blocks-2026-08-25.md (the L-01..L-14 blocker register). State as of 2026-08-26, commit 72543649 on main (type-check and build both pass there): - Steps 1, 2, 3, 7, 8 are DONE and their own checks passed. - Step 4 is DONE; re-run its verify once to confirm, then close it. - Steps 5, 6, 9 are PARTIAL. They were killed while writing. Re-run each one WHOLE. - Steps 10, 11, 12 have not started. - Steps 13, 14, 15, 16 are GATED. Do not run them. Known weakness carried forward: the duplicate-budget guard is look-it-up-then-create, two separate calls. Two workers applying the same approval at once could still create two budgets and two spend ceilings. Only step 10's atomic claim closes that. Activate nothing before then. Run it with: /tier <dev root>/hub/docs/plans/finish-the-ads-control-plane-and-launch-safely.md 5,6,9,10,11,12 Rules: never push, never deploy, never apply a migration to a live database, never call a Google Ads or Meta write API against a real account, never send email, never replace a secrets file. Migration files only. Report the worst flaw in your own work at the end.
Steps 2-11 can start today. Step 1 needs the hosting login from the owner.
Run the Gacka16 rebuild plan in the gacka repo. Plan file: <dev root>/gacka/docs/plans/rebuild-gacka16-as-a-fast-site-the-office-can-edit.md Read it first, plus docs/rebuild-decision-2026-08-24.md, docs/server-report-2026-08-24.md and docs/broken-images-on-live-pages-2026-08-26.md. Ground truth: 26 pages, 5 posts, all 187 pictures already saved under site-export/. Prices are already published on the live site — do not treat them as missing. The contact form is an embedded Google Form and keeps working untouched. The server cannot run a live app, so the site must publish as plain finished files. Google Tag Manager GTM-K7GB8S5X must survive. Decisions already made, do not reopen: every page stays; the office edits through Decap with free GitHub logins; nothing on the old site gets touched; no booking at launch. Still needed from the owner: real dates for anything actually happening. Invent no date, price or event — show a past event as past until real dates arrive. Run it with: /tier <dev root>/gacka/docs/plans/rebuild-gacka16-as-a-fast-site-the-office-can-edit.md 2,3,4,5,6,7,8,9,10,11 Step 1 (publishing access) is blocked until the owner hands over the hosting login. Steps 12, 15 and 16 are gated — they change or retire the live site. Do not run them.
A directional public-footprint score based on discoverability, trust, account control, tracking and freshness—not a Google metric.
Best positioned for celebration demand
Strong local proof, weak brand clarity
Wix site and checkout are live · Google mail routing is incomplete · no SPF detected · DMARC monitoring only · no tracking of any kind on the homepage.
Legacy WordPress on a 2016 server that cannot run a modern site · full Google Workspace mail · SPF present · no DMARC · GTM-K7GB8S5X, which the rebuild must carry across.
Neither Facebook Page is running ads in Croatia, and no ad account exists for either brand yet. Nothing can spend money today.
Every verified public account and link. Private administrators, billing and recovery methods require authenticated access.
Keyword Planner, Search Console queries, conversions and private Meta ad-account IDs will populate after the Chrome extension is connected in Settings → Computer use.
ULIX D.O.O. · Miramarska 26, Zagreb
Travel Management d.o.o. · public site identity
Feštaj: no Threads, X/Twitter or Pinterest. Gacka16: no separate Instagram, LinkedIn, TikTok, YouTube, Threads or X account verified; the official site links only Facebook.
Prioritized from current Google Croatia autocomplete prominence and live search-result evidence. These are demand tiers, not fabricated monthly volumes.
Feštaj acquisition cluster
Gacka acquisition cluster
Exact monthly searches, CPC and competition are intentionally blank until the signed-in Google Ads profile is reachable. Search Console will then show which of these terms already produce impressions and clicks for each domain.
All five candidates returned no current .com registration record in the Verisign RDAP check on 25 Aug 2026. Availability can change at any moment.
Short enough to remember. Clear enough to understand. Broad enough to unite events, celebrations, coworking, offices, education and meetings.
The strongest umbrella for celebrations, coworking, meetings and corporate events. Immediate in both markets.
94Crystal clear for event buyers and international visitors, but narrower for coworking and virtual office.
88Short and locally natural. Keeps the address equity, but needs English explanation for visitors.
82Seven letters before .com and easy locally. “ZG” is weaker for international recognition.
77Warm and memorable, but lower instant category clarity and weaker Croatian search alignment.
72Google says keywords in a domain alone have hardly any ranking effect. The SEO value comes from a memorable site name, strong local proof, helpful landing pages, clean redirects and content that matches search intent.
Google’s own guidance ↗One brand, one domain, separate pages for each job the customer is trying to complete.
/najam-prostora-za-proslave-zagreb/proslava-rodendana-zagreb/najam-dvorane-zagreb/coworking-zagreb/virtualni-ured-zagreb/meeting-room-zagreb/team-building-zagreb/en/event-venue-zagrebSequence ownership and measurement first, then migration, then paid acquisition.