HomeCase StudiesNine NYC Dining Sites, One Publishing Workflow
AI Consulting

Nine NYC Dining Sites, One Publishing Workflow

NetSys built a nine-site dining network with scheduled publishing informed by keyword research. Reported average monthly visits to the main site rose from 21 to about 84.

ServiceAI consulting and publishing automation
IndustryRestaurants and hospitality
ScaleNine dining websites
RegionNew York City
TimelineScheduled publishing and ongoing measurement
The Challenge

The main restaurant website averaged 21 visits a month. The team wanted to reach people earlier, while they were looking for an Italian restaurant by neighborhood or planning an occasion such as a birthday or private dinner.

Those searches call for different information. The challenge was to serve those readers with distinct publications while keeping hosting, analytics and publishing manageable for one team.

What NetSys Did

The approach

1

Give each site a reader and a job

Nine sites cover separate dining interests, including Italian dining in individual neighborhoods, private dining and birthday dinners. Keyword research informs the topic queue, and each publication has its own editorial charter for subject, voice and format.

2

Build one shared operating system

One Next.js application and Postgres database route visitors to the right publication by hostname. Each site has its own design and content, while one dashboard manages drafts, publishing and traffic. Site-level analytics allow the operator to see what individual publications attract.

3

Schedule the publishing rotation

A scheduled task on a Claude subscription uses the publishing connection to read the site charter and recent posts, choose a relevant topic from keyword research, and publish through the shared application. Checking recent topics helps each publication avoid repeating its own coverage.

4

Measure the network and the main site separately

The project tracks the combined readership of the nine publications and the average monthly visits to the main restaurant site. Those are different measures, which makes it possible to see whether the network has an audience and whether the main site is getting more visits.

Deployed Stack
  • Next.js across nine domains
  • Postgres content and site registry
  • Claude scheduled publishing
  • Editorial charters and keyword research
  • First-party traffic reporting
Measured Outcomes

The results

4×
Reported average monthly main-site visits, from 21 to about 84 after launch
100+
Average daily visits across the nine publications combined, as reported for this engagement
9
Dining publications managed from one publishing system
Average monthly visits to the main site (visits per month)
0255075100Before the networkAfter launch0255075100Before the networkAfter launch

Figures supplied for this engagement. The after-launch figure is approximate. The chart excludes the separate daily traffic across the nine publications.

View data table
CategoryMain-site visits (visits per month)
Before the network21
After launch84
AI Consulting

Discuss ai consulting for your business.

Tell us about your current systems, the result you need and your timeline. We will discuss the work, responsibilities and pricing before you decide on an engagement.