SaaS

Açık Kaynak SEO

warningProblem

"I'm losing the SEO battle for my own open source project"

psychologyPotansiyel Çözüm

Açık kaynak projelerin kendi isimleriyle yapılan aramalarda SEO rekabetinde yaşadığı zorluklara çözüm sunan, proje sahiplerine özel SEO optimizasyon araçları ve danışmanlık hizmetleri sağlayan bir platform.

groupHedef Kitle

Kendi açık kaynak projelerinin SEO performansını artırmak isteyen geliştiriciler, proje yöneticileri ve açık kaynak toplulukları.

paymentsGelir Modeli

Abonelik tabanlı (freemium model ile temel özellikler ücretsiz, gelişmiş analizler ve destek ücretli), danışmanlık hizmetleri.

Aksiyon Planı

Proje adı için anahtar kelime analizi ve önerileri

Rakip açık kaynak projelerin SEO profili analizi

Temel on-page SEO optimizasyon rehberleri

Proje web sitesi için temel teknik SEO denetimi

Basit backlink analizi ve önerileri

Pazar Analizi

7.8Puan

Kaynak: Hacker Newsopen_in_new

AI Prompt

You are a skilled full-stack developer tasked with building a single-page application (SPA) for an open-source SEO support platform. The goal is to help open-source project maintainers improve their project's visibility in search engine results. The application should be built using a modern JavaScript framework (like React, Vue, or Svelte) and styled with Tailwind CSS for a clean, responsive design.

**Core Functionality:**
1. **Project Input:** A form where users can input their open-source project's name and optionally its GitHub repository URL or project website.
2. **Keyword Analysis:** Based on the project name, suggest relevant keywords and analyze their search volume and competition. This will involve integrating with a keyword research API (you can mock this for the MVP or use a free tier if available).
3. **Competitor Analysis:** Fetch and display basic SEO data for similar open-source projects. This might include domain authority (mocked), backlink count (mocked), and top ranking keywords (mocked).
4. **On-Page SEO Suggestions:** Provide actionable tips for on-page optimization relevant to open-source projects (e.g., README optimization, clear project descriptions, proper tagging).
5. **Technical SEO Audit (Basic):** A simple audit of the project's website (if provided) checking for common issues like mobile-friendliness, page speed (mocked), and sitemap availability.
6. **Reporting:** A clean, summarized report of the analysis and suggestions.

**Technical Requirements:**
* **Frontend Framework:** Choose one (React, Vue, Svelte) and stick to it. Use functional components and hooks/composition API.
* **Styling:** Tailwind CSS for utility-first styling.
* **State Management:** Use the framework's built-in state management or a simple library like Zustand/Pinia if necessary.
* **Routing:** Implement client-side routing for different sections (e.g., input, analysis results, suggestions).
* **API Integration:** Design the application to easily integrate with external APIs (even if mocked for now). Use `fetch` or `axios`.
* **Responsive Design:** Ensure the UI is usable on various screen sizes.
* **User Experience:** Prioritize a clean, intuitive user interface. Loading states and clear feedback are essential.

**MVP Scope (Focus on core value):**
* Mock API responses for keyword data, competitor data, and technical SEO metrics. The focus is on the UI/UX and application structure.
* Do not implement user authentication or database storage in the MVP. Focus on the single-page analysis flow.
* The primary output should be a clear, visual report presented to the user.

**Code Structure:**
Organize the code into logical components (e.g., `InputForm`, `KeywordAnalysis`, `CompetitorTable`, `OnPageSuggestions`, `SeoReport`). Use clear naming conventions. Ensure the code is well-commented where necessary.

**Deliverable:**
Generate the complete HTML, CSS (Tailwind classes), and JavaScript code for this single-page application. Assume a basic project setup where you can place the code.