8890e61c2e
Three connected fixes:
1) Stop the unwanted "translate this page to Portuguese?" popup that
some US users were seeing. Chrome's content-language detector was
mis-firing on imported BB articles that mention Portuguese/Spanish
company/person names. Add to layout <head>:
<meta name="google" content="notranslate" />
<meta http-equiv="Content-Language" content="en" />
<meta name="robots" content="index, follow" />
Together with the existing <html lang="en"> this is the standard
"this site is English, don't offer to translate" signal.
2) Wire the LanguageSwitcher pulldown to actually do something. It used
to set a cookie + flip <html lang> with no effect on visible
content. Now picking a non-English language redirects the current
URL to Google Translate's hosted proxy (e.g.
https://broadcastbeat-com.translate.goog/<path>?_x_tr_sl=en
&_x_tr_tl=es&_x_tr_hl=en
), which renders the entire page translated server-side by Google
and preserves the user's session as they navigate. English stays
on the canonical broadcastbeat.com host.
3) SEO posture: English is the only indexable version. The Google
Translate proxy lives on a different (Google-owned) domain so US
browsers and Googlebot only ever see the English content. The
alternates.languages hreflang block stays absent — re-add only once
real translated routes exist (Phase D).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Next.js
A modern Next.js 15 application built with TypeScript and Tailwind CSS.
🚀 Features
- Next.js 15 - Latest version with improved performance and features
- React 19 - Latest React version with enhanced capabilities
- Tailwind CSS - Utility-first CSS framework for rapid UI development
🛠️ Installation
- Install dependencies:
npm install
# or
yarn install
- Start the development server:
npm run dev
# or
yarn dev
- Open http://localhost:4028 with your browser to see the result.
📁 Project Structure
nextjs/
├── public/ # Static assets
├── src/
│ ├── app/ # App router components
│ │ ├── layout.tsx # Root layout component
│ │ └── page.tsx # Main page component
│ ├── components/ # Reusable UI components
│ ├── styles/ # Global styles and Tailwind configuration
├── next.config.mjs # Next.js configuration
├── package.json # Project dependencies and scripts
├── postcss.config.js # PostCSS configuration
└── tailwind.config.js # Tailwind CSS configuration
🧩 Page Editing
You can start editing the page by modifying src/app/page.tsx. The page auto-updates as you edit the file.
🎨 Styling
This project uses Tailwind CSS for styling with the following features:
- Utility-first approach for rapid development
- Custom theme configuration
- Responsive design utilities
- PostCSS and Autoprefixer integration
📦 Available Scripts
npm run dev- Start development server on port 4028npm run build- Build the application for productionnpm run start- Start the development servernpm run serve- Start the production servernpm run lint- Run ESLint to check code qualitynpm run lint:fix- Fix ESLint issues automaticallynpm run format- Format code with Prettier
📱 Deployment
Build the application for production:
npm run build
📚 Learn More
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API
- Learn Next.js - an interactive Next.js tutorial
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
🙏 Acknowledgments
- Built with Rocket.new
- Powered by Next.js and React
- Styled with Tailwind CSS
Built with ❤️ on Rocket.new