ng add @angular/seo

Open
#12,120 23 comments 30 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
angular, typescript
Domain
cli, tooling

Research direction

Start by reviewing the Angular CLI schematics area and the ng add flow described in the issue. Break the request into the listed SEO features—robots.txt, sitemap.xml, crawler polyfills, error logging, and noindex handling—and clarify scope and acceptance criteria before changing anything; no files or tests are named.

Written by the indexing model from the issue text.

Description

area: @schematics/angular feature feature: under consideration

From @IgorMinar on April 18, 2018 10:7

Bug Report or Feature Request (mark with an x)
- [ ] bug report -> please search issues before submitting
- [x] feature request
Area
- [ ] devkit
- [x] schematics
Versions

v6

Desired functionality

I'd like to be able to invoke ng add @angular/seo and have the CLI make my application search engine friendly. Initially I'd like to see the following feature provided by the schematics:

  • generate robots.txt with no rules but a simple instructions/link on how to setup blacklist rules
  • generate sitemap.xml with similar documentation/links as in robots.txt
  • add code that would feature detect and conditionally load polyfills needed by the crawlers
  • setup error logging via global error handler with an option to redirect the output to a remote server
  • provide facilities to easily add and remove the noindex metadata to emulate the HTTP 404 and 500 status codes
Mention any other details that might be useful

Copied from original issue: angular/devkit#729

Dominant language
TypeScript
Stars
27k
Forks
11.8k
Avg merge
16h 35m
Merged PRs (30d)
176

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from angular/angular-cli

All issues in angular/angular-cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.