Answers.Body: <p>Can't think of a native way to do this — a few options come to mind, none of which are ideal.</p>
  
  <ol>
  <li>recreate your sites 404 page in your 404 template (should be able to just copy/paste for the most part).</li>
  <li><p>redirect to your site's 404 page from your 404 template (i.e. redirect 'craft/templates/404.html' to 'mydomain.com/404.html'). So in your 404 template you would have:</p>
  
  <pre><code>{%  redirect '/404.html'  %}
  </code></pre></li>
  <li><p>Reaching here, but you could also possibly include your 404 page in an iframe in your 404 template.</p></li>
  </ol>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-15T03:39:01.430Z
Answers.LastActivityDate: 2016-07-07T05:33:48.037Z
Answers.LastEditDate: 2016-07-07T05:33:48.037Z
Answers.UserDisplayName: Douglas McDonald
Answers.Body: <p>If your current 404 page is a static HTML page, I think the simplest solution would be to just copy your existing 404 HTML page into the craft/templates folder. Craft will display an HTML page just as easily as Twig code. Just make sure the file is named <code>404.html</code> in your craft/templates folder.</p>
  
  <p>If you make a change to the 404 page later, you would have to change it in two places, but that's really the only downside I can think of.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-16T16:33:51.973Z
Answers.Text: I am just wondering how that will affect URL errors on Google.
Answers.UserDisplayName: Steve VH
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-16T17:38:59.357Z
Answers.Text: SEO-wise it works the same to your current 404. Google would request a bad link like `http://buildwithcraft.com/misspelled-docz/` and receive the 404 error and 404 page content back from the server. But the URL doesn't change to `/404.html`. It's stays the same as the requested URL. That's how an Apache server would deal with the error too.
Answers.UserDisplayName: Alex Roper
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-16T06:27:08.270Z
Answers.LastActivityDate: 2015-04-16T17:40:36.440Z
Answers.LastEditDate: 2015-04-16T17:40:36.440Z
Answers.UserDisplayName: Alex Roper
Body: <p>I am using Craft <strong>only for the blog section</strong> of my site. The rest is HTML.</p>
  
  <p>How do I make my site's 404 page come up for errors in the Craft-blog section?</p>
  
  <p>Do I use the errorTemplatePrefix?</p>
  
  <p>Where does that go?</p>
  
  <p>What to I put in there if Craft is above root and my page is mydomain.com/404.html</p>
  
Tags: <404>
Title: How to use my site's 404 page?
ThreadText: # How to use my site's 404 page?
  
  (Asked by: username_0 on 2015-04-14)
  
  I am using Craft **only for the blog section** of my site. The rest is HTML.
  
  How do I make my site's 404 page come up for errors in the Craft-blog section?
  
  Do I use the errorTemplatePrefix?
  
  Where does that go?
  
  What to I put in there if Craft is above root and my page is mydomain.com/404.html
  
  **Tags:** 404
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2015-04-15. Score: 1
  
  Can't think of a native way to do this — a few options come to mind, none of which are ideal.
  
  1. recreate your sites 404 page in your 404 template (should be able to just copy/paste for the most part).
  2. redirect to your site's 404 page from your 404 template (i.e. redirect 'craft/templates/404.html' to 'mydomain.com/404.html'). So in your 404 template you would have:
  
     ```
     {%  redirect '/404.html'  %}
  
     ```
  3. Reaching here, but you could also possibly include your 404 page in an iframe in your 404 template.
  
  
  ---
  
  ### Answer by username_2 on 2015-04-16. Score: 1
  
  If your current 404 page is a static HTML page, I think the simplest solution would be to just copy your existing 404 HTML page into the craft/templates folder. Craft will display an HTML page just as easily as Twig code. Just make sure the file is named `404.html` in your craft/templates folder.
  
  If you make a change to the 404 page later, you would have to change it in two places, but that's really the only downside I can think of.
  
  > **Comments:**
  > **username_0**: I am just wondering how that will affect URL errors on Google.  
  > **username_2**: SEO-wise it works the same to your current 404. Google would request a bad link like `http://buildwithcraft.com/misspelled-docz/` and receive the 404 error and 404 page content back from the server. But the URL doesn't change to `/404.html`. It's stays the same as the requested URL. That's how an Apache server would deal with the error too.  
  
  ---
  
  