Now, Visualforce has some very useful attributes to resolve these issues on apex:page tag. We can utilize them if building Angular app.
Refer the document apex:page tag.
On the apex page tag, provide attributes this way:
<apex:page docType="html-5.0" showheader="false" sidebar="false" standardstylesheets="false" applyHTMLTag="false" applyBodyTag="false">
<html lang="en">
<head>
<meta charset="UTF-8"/>
<meta name="viewport" content="width=device-width, initial-scale=1"/>
<title>Example - example-guide-concepts-1-production</title>
</head>
<body>
<c:AngualarApp/>
</body>
</html>
</apex:page>
Above will be rendered as no conflict HTML:
<!DOCTYPE HTML>
<html lang="en">
<head>
<script src="/static/111213/js/perf/stub.js" type="text/javascript"></script>
<script src="/jslibrary/1466812160000/sfdc/VFMetadataSender.js" type="text/javascript"></script><meta HTTP-EQUIV="PRAGMA" CONTENT="NO-CACHE" />
<meta HTTP-EQUIV="Expires" content="Mon, 01 Jan 1990 12:00:00 GMT" />
<meta charset="UTF-8" />
<meta content="width=device-width, initial-scale=1" name="viewport" />
<title>Example - example-guide-concepts-1-production</title>
</head>
<body>
</body>
</html>
<script type="text/javascript"> SfdcApp.Visualforce.viewstate.ViewstateSender.sendViewstate('https://ashwaniarea-dev-ed.my.salesforce.com', 'NoDefaultHTMLTags'); </script>